09-21-2009 03:27 PM
Hi all,
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!
09-22-2009 04:08 PM
Minurc, this is a known issue; we're trying to get a fix into a maintenance release for both 6.0 and 6.3. Make sure you have a ticket open with support for this so you'll get notified when the fix is available!
09-22-2009 04:18 PM
Ok, didn't know that fact. Just came across while testing appliance, and did read known issues for 6.0 and 6.3, but didn't find one explaining it :)
But it's good to know that it's in progress. Thanks.
09-22-2009 09:47 PM
Yes, we found the issue too late to include it in the 6.0.1 release notes, unfortunately.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide