/* IMPORTANT INFORMATION:
* HttpWebRequest has a bug where if a 302 redirect is encountered (such as from a Response.Redirect), any cookies
* generated during the request are ignored and discarded during the internal redirect process. The headers are in
* fact returned, but the normal process where the cookie headers are turned into Cookie objects in the cookie
* container is skipped, thus breaking the login processes of half the sites on the internet.
*
* The workaround is as follows:
* 1. Turn off AllowAutoRedirect so we can intercept the redirect and do things manually
* 2. Read the Set-Cookie headers from the response and manually insert them into the cookie container
* 3. Get the Location header and redirect to the location specified in the "Location" response header
*
* Worth noting that even if this bug has been solved in .Net 4 (I haven't checked) we should still use manual
* redirection so that we can properly log responses.
Basically, Microsoft fucked up with their implementation of HttpWebRequest in .NET framework, so I have to write my own cookie parser. Fuck, the shit I waste time on. Took me forever to track this down too
FUUUUUUUUUUUUUUUUUUUUCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK YOU AND YOUR FUCKING CUSTOM FUCKING HTTP HEADERS FUCKING AJAX FUCKING SHIT FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
Parsing a cookie shouldn't be any problem at all, no?!
Still microsoft fucking something this "simple" up is pretty interesting! I supposed that it took more time to think of work arounds and writing them down, then actually fixing the problem
Parsing a cookie shouldn't be any problem at all, no?!
Still microsoft fucking something this "simple" up is pretty interesting! I supposed that it took more time to think of work arounds and writing them down, then actually fixing the problem
Actually it took me the most time to FIND the fucking problem, because it still blows my mind that something as BASIC as HANDLING THE FUCKING COOKIES WASN'T PROPERLY FUCKING IMPLEMENTED?
Who the fuck do they have testing the code over there? Mentally incapacitated monkeys? FUCK.
But I've calmed down a bit. Slept a bit. Should be fine now. I fixed the problem, but still have problems logging into Gmail. Expect additional rage by tonight.
Signature/Avatar nuking: none (can be changed in your profile)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
