W
wizofaus
If you use your browser to navigate to http://www.fsa.gov.uk/register/,
it will redirect you to http://www.fsa.gov.uk/register/home.do;jessionid=
etc. etc. etc.
But if you use WebRequest to fetch that initial URL, the response URL
is "http://xdsapvip:3006/register/WEB-INF/jsp/layouts/base.jsp"!
This is actually the content of the HTTP "content-location" header,
which as I understand it, is only for identification of where as
resource came from, not of a valid URL that could/should be used to
access the resource externally.
In fact, it appears there's no way of getting the redirected URL that
is shown in your browser other than turning off the automatic
redirection flag and grabbing the "Location" http header directly from
the initial response.
Is there any way of turning off this processing of the "content-
location" header? Or is it fixed in .Net 2.0 (which I'm migrating to
ASAP)?
it will redirect you to http://www.fsa.gov.uk/register/home.do;jessionid=
etc. etc. etc.
But if you use WebRequest to fetch that initial URL, the response URL
is "http://xdsapvip:3006/register/WEB-INF/jsp/layouts/base.jsp"!
This is actually the content of the HTTP "content-location" header,
which as I understand it, is only for identification of where as
resource came from, not of a valid URL that could/should be used to
access the resource externally.
In fact, it appears there's no way of getting the redirected URL that
is shown in your browser other than turning off the automatic
redirection flag and grabbing the "Location" http header directly from
the initial response.
Is there any way of turning off this processing of the "content-
location" header? Or is it fixed in .Net 2.0 (which I'm migrating to
ASAP)?