You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
one example use case may be doing nginx reverse proxying using WebSockets where the encrypted ips are passed in the header when the first response is sent from the server to the client and further the next following requests from the same client come with encrypted ip in the header, which nginx decodes and then routes the request to the correct downstream server with the ip same as we got after decrypting the (encrypted)ip from the header in the request (on load balancer or nginx).
In the above case we want to have the encryption logic on the server side and decryption logic on the load balancer (nginx) side.
The text was updated successfully, but these errors were encountered:
one example use case may be doing nginx reverse proxying using WebSockets where the encrypted ips are passed in the header when the first response is sent from the server to the client and further the next following requests from the same client come with encrypted ip in the header, which nginx decodes and then routes the request to the correct downstream server with the ip same as we got after decrypting the (encrypted)ip from the header in the request (on load balancer or nginx).
The text was updated successfully, but these errors were encountered: