Its true that redirects to another host are very common. HttpMethod is very anal about not redirecting to a new host or port or protocol. The RFCs certainly allow that. There was state information that made it unrealistic to forward outside the current connection.

But a lot has changed, there is no "session" concept anymore. This functionality should be relatively easy to implement. Any takers?

I've created a bug report for this:
http://issues.apache.org/bugzilla/show_bug.cgi?id=1672

Jandalf.


Alan Marcinkowski wrote:



Repost from Commons. Sorry, didn't know there was a specific HttpClient list...

Hello,

I dug through the code to see why my redirects were not being followed. I found HttpMethodBase:checkValidRedirect was not honoring cross server redirects. Isn't this a common type of redirect? Is there a reason its not supported? I did a lot of digging in the specs and couldn't find anything wrong with it unless its an architectural issue with the HttpMethod and the way it integrates with the session. Any help would be appreciated. If there is no reason not to support it, can you make that check part of the "strict mode" settings on the object?

Thanks in advance,

Alan





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to