Redirection mechanism is widely used in proxy-based scenario.
Currently when multiple servers share one proxy, proxy forwards all the packets between servers and clients. Thus, the proxy adds latency, take many computing resources and impacts the overall performance. Especially for short connections scenarios like WordPress, the latency can be a critical issue.
Supporting redirection mechanism is helpful for proxy-based scenario. It is more like HTTP redirects  or Oracle redirected connections . Clients get the servers’ address from proxies and connect to servers transparently without latency and computing resource wasted.
Client/Server Protocol change needs both client and server support.
Ending connection OK_Packet info field might contain redirection information.
Either connector support redirection mechanism and will close current connection and redirect to indicated value, or if not supporting redirection (or redirection is disable) then driver will continue using current connection.
There is no recursion, meaning that connector that have been redirect will not take another redirection in account.
info field format is then:
specific redirection option:
|user||if set, must superseed connection user.|
|ttl||validity timeout in second. This permit caching redirection client side. 0 means no caching 'default'|