Not easy to get it from the RFCs or from the online discussions,
Can we please make a final decision if further redirect changes are needed now,
just doing other updates.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Not easy to get it from the RFCs or from the online discussions,
but I've now checked how Firefox and Chrome are implementing it
Exactly, each browser has implemented redirection in different ways for
different requests, there is no general consensus
If you can just check MSIE as well,
This subject doesn't deserve not even a reply?!
I'm the only one able to fix things here at the moment, and I have a lot of
other priorities. But I'll put it on my list for next month.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
But I'll put it on my list for next month.
OK Angus. Thanks.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
This subject doesn't deserve not even a reply?!
If the problem is where to try it, here is an online service to test
HTTP redirects
http://jigsaw.w3.org/HTTP/300/
Just put the next URL in the OverbyteIcsHttpTst application, and issue a
POST request (without any data).
Hi everyone,
The 307 and 308 redirects must maintain the same request method, and not
revert to GET as with other redirects.
This can be handled by changing, in the unit OverbyteIcsHttpProt methods
LocationSessionClosed and StartRelocation, the line:
if FRequestType = httpPOST then
