http://bugs.winehq.org/show_bug.cgi?id=18384
--- Comment #40 from Erich Hoover ehoover@mines.edu 2009-06-09 19:18:33 --- (In reply to comment #39)
...
My findings - while the \n\n bug IS a wininet bug, the actual source of the 500 is not. It seems that the server is expecting something in particular from the request and the actual script bails (painfully) once it sees it doesn't get it.
Now we really need the wininet log from windows. Until then, I don't see how this bug can move forward.
If anyone actually has Windows, I created an attachment (id=21616) that should intercept the calls to the wininet DLL before they are encrypted.