T
TK
I'm using HttpWebRequest (with HEAD) to check for broken links on
certain websites. I'm receiving several 400 bad request responses.
With a network sniffer i can see that the initial response is a 301
(moved permanently). Then HttpWebRequest tries another request using
the url given in the response (since request.AllowAutoRedirect=true by
default). This second request causes the 400 (bad request) response
because the url is not encoded before the request is sent.
I encode the url explicitly before making the initial request but the
second request happens behind the scenes. Is there a way to avoid this
error, by somehow encoding the url of a request generated due to a
redirection?
Has anyone else encountered this problem, any suggestions, solutions?
Thanks,
TK
certain websites. I'm receiving several 400 bad request responses.
With a network sniffer i can see that the initial response is a 301
(moved permanently). Then HttpWebRequest tries another request using
the url given in the response (since request.AllowAutoRedirect=true by
default). This second request causes the 400 (bad request) response
because the url is not encoded before the request is sent.
I encode the url explicitly before making the initial request but the
second request happens behind the scenes. Is there a way to avoid this
error, by somehow encoding the url of a request generated due to a
redirection?
Has anyone else encountered this problem, any suggestions, solutions?
Thanks,
TK