David
Fri Feb 04 22:44:34 CST 2005
A 400 error indicates that the application sent an invalid HTTP request to
the server.
If I had to guess, I would say that the SunJVM output stream is probably
using \n as line delimiters for HTTP (invalid according to RFC2616 spec,
though some servers inappropriately accepts them, including IIS5). IIS6
requires \r\n (as spec'd in RFC) for the request, thus returns 400 for such
requests.
The correct thing is to ensure that the client sends properly formatted HTTP
requests regardless of the underlying JVM.
A network sniff of the request/response should show exactly what is "400"
about it. Network Monitor ships with Windows Server 2003 in Add/Remove
Programs so you can easily install it for network diagnosis.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"kflemingrcm1" <kflemingrcm1@discussions.microsoft.com> wrote in message
news:CB8D6529-0BBF-4BE3-8FA4-AFC7EEB2A10E@microsoft.com...
If I use the MSJVM on XP it can load a java applet that does a post with no
problem.
Same code using SunJVM and IIS6 returns error 400 and closes the socket
while IIS5 has no problem with accepting post from applet regardless of JVM
used.
Remember...no code change. Just JVM and IIS