Consider next scenario:
- deployment mode explicit forward
- proxy port not 80
- authentication surrogate is session cookie
This should work like this:
Client sends request, WSA replies 307 with "Location" header that redirects to itself (WSA) with an internal path which should result in retrieving content if authorized.
Problem occurs in header, "Location" directive, because it does not return configured proxy port, just hostname (eg: Location: http://proxy/internal_path/web_site).
Workaround for this is to configure port 80 as proxy port as well.
Tested on AsyncOS 6.0, 6.3!