HTTP 1.1 400 Bad request

David, thanks for the reply. We still get the error even
when JRUN service is stopped.

Thanks and Regards
Sridhar

 >-----Original Message-----
 >Do you get any problems with POST method if JRUN is not
active? If so, this
 >is a JRUN issue.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"sridhar@emacmillan.com"
<anonymous DeleteThis @discussions.microsoft.com> wrote in
 >message news:14ac01c3f261$3ae68040$3501280a@phx.gbl...
 >Hi,
 >
 >We have installed Jrun4.0 in Win 2k and its running along
 >with IIS 5.0. Presently a request to any website hosted in
 >the server from Netscape 7.1 in PC or IE 5.2 in Mac we get
 >this error "HTTP/1.1 400 Bad request".
 >
 >This happens only when the HTTP request uses POST method.
 >As we are aware that JRUN gets the HTTP request and then
 >forwards it to IIS, we feel that there could be a problem
 >here.
 >
 >PS: In case there is a proxy server then this works fine,
 >only when there is direct connection then this error
 >results.
 >
 >Thanks and Regards
 >Sridhar
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP 1.1 400 Bad request 

I'm referring to the ISAPI Filter that JRUN installs -- did you make sure it
is still not active.

My suspicion is that something on your server is modifying/parsing HTTP
incorrectly, causing IIS to think something is a new request when it isn't,
thus triggering the 400 Bad Request (Verb). ISAPI Filters can do this, so I
want you to disable all your ISAPI Filters. In particular, I know that JRUN
tries to hijack all requests from IIS, so it is a prime suspect. If it does
it incorrectly (for example, IE can do pipelined HTTP requests (part of HTTP
spec), which JRUN may be botching up), it could cause this problem -- in
which case this is a JRUN bug that you need to find support for.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Sridhar" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
news:10c6901c3f3d9$bf1800e0$a601280a@phx.gbl...
David, thanks for the reply. We still get the error even
when JRUN service is stopped.

Thanks and Regards
Sridhar

 >-----Original Message-----
 >Do you get any problems with POST method if JRUN is not
active? If so, this
 >is a JRUN issue.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"sridhar@emacmillan.com"
<anonymous RemoveThis @discussions.microsoft.com> wrote in
 >message news:14ac01c3f261$3ae68040$3501280a@phx.gbl...
 >Hi,
 >
 >We have installed Jrun4.0 in Win 2k and its running along
 >with IIS 5.0. Presently a request to any website hosted in
 >the server from Netscape 7.1 in PC or IE 5.2 in Mac we get
 >this error "HTTP/1.1 400 Bad request".
 >
 >This happens only when the HTTP request uses POST method.
 >As we are aware that JRUN gets the HTTP request and then
 >forwards it to IIS, we feel that there could be a problem
 >here.
 >
 >PS: In case there is a proxy server then this works fine,
 >only when there is direct connection then this error
 >results.
 >
 >Thanks and Regards
 >Sridhar
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP 1.1 400 Bad request 

Hi,

Thanks for the reply. We removed ISAPI filter and also
uninstalled JRUN. Still getting the same error.

Thanks and Regards
Sridhar

 >-----Original Message-----
 >I'm referring to the ISAPI Filter that JRUN installs --
did you make sure it
 >is still not active.
 >
 >My suspicion is that something on your server is
modifying/parsing HTTP
 >incorrectly, causing IIS to think something is a new
request when it isn't,
 >thus triggering the 400 Bad Request (Verb). ISAPI
Filters can do this, so I
 >want you to disable all your ISAPI Filters. In
particular, I know that JRUN
 >tries to hijack all requests from IIS, so it is a prime
suspect. If it does
 >it incorrectly (for example, IE can do pipelined HTTP
requests (part of HTTP
 >spec), which JRUN may be botching up), it could cause
this problem -- in
 >which case this is a JRUN bug that you need to find
support for.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Sridhar" <anonymous.RemoveThis@discussions.microsoft.com> wrote in
message
 >news:10c6901c3f3d9$bf1800e0$a601280a@phx.gbl...
 >David, thanks for the reply. We still get the error even
 >when JRUN service is stopped.
 >
 >Thanks and Regards
 >Sridhar
 >
  >>-----Original Message-----
  >>Do you get any problems with POST method if JRUN is not
 >active? If so, this
  >>is a JRUN issue.
  >>
  >>--
  >>//David
  >>IIS
  >>This posting is provided "AS IS" with no warranties, and
 >confers no rights.
  >>//
  >>"sridhar@emacmillan.com"
 ><anonymous.RemoveThis@discussions.microsoft.com> wrote in
  >>message news:14ac01c3f261$3ae68040$3501280a@phx.gbl...
  >>Hi,
  >>
  >>We have installed Jrun4.0 in Win 2k and its running along
  >>with IIS 5.0. Presently a request to any website hosted
in
  >>the server from Netscape 7.1 in PC or IE 5.2 in Mac we
get
  >>this error "HTTP/1.1 400 Bad request".
  >>
  >>This happens only when the HTTP request uses POST method.
  >>As we are aware that JRUN gets the HTTP request and then
  >>forwards it to IIS, we feel that there could be a problem
  >>here.
  >>
  >>PS: In case there is a proxy server then this works fine,
  >>only when there is direct connection then this error
  >>results.
  >>
  >>Thanks and Regards
  >>Sridhar
  >>
  >>
  >>.
  >>
 >
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP 1.1 400 Bad request 

400 Bad Request is pretty much indicative of something wrong that the client
browser is doing (or a buggy ISAPI Filter that modified the request
incorrectly on the server). It is rarely an issue with the web server (web
server is simply telling you "I'm getting a bad request!", so you need to
start looking at what's sending it the bad request and fixing that.

Get a NetMon network trace of the actual request that the server received
and post that here.

JRUN is something that runs on IIS and forwards request to a Java VM to be
executed, so it can be a cause of the above. To be absolutely certain, JRUN
CANNOT FORWARD ANYTHING TO IIS TO EXECUTE.

For example, if you send a POST request, did it have a Content-Length header
and entity body when it reached IIS? A POST request without Content-Length
is an invalid request. Also, if request headers are not terminated with
\r\n , that is also invalid. Etc. In all these cases, it's a client-side
problem; server is merely throwing up the red flag.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"sridhar" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
news:119df01c3f5d2$2c2d7620$a301280a@phx.gbl...
Hi,

Thanks for the reply. We removed ISAPI filter and also
uninstalled JRUN. Still getting the same error.

Thanks and Regards
Sridhar

 >-----Original Message-----
 >I'm referring to the ISAPI Filter that JRUN installs --
did you make sure it
 >is still not active.
 >
 >My suspicion is that something on your server is
modifying/parsing HTTP
 >incorrectly, causing IIS to think something is a new
request when it isn't,
 >thus triggering the 400 Bad Request (Verb). ISAPI
Filters can do this, so I
 >want you to disable all your ISAPI Filters. In
particular, I know that JRUN
 >tries to hijack all requests from IIS, so it is a prime
suspect. If it does
 >it incorrectly (for example, IE can do pipelined HTTP
requests (part of HTTP
 >spec), which JRUN may be botching up), it could cause
this problem -- in
 >which case this is a JRUN bug that you need to find
support for.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Sridhar" <anonymous RemoveThis @discussions.microsoft.com> wrote in
message
 >news:10c6901c3f3d9$bf1800e0$a601280a@phx.gbl...
 >David, thanks for the reply. We still get the error even
 >when JRUN service is stopped.
 >
 >Thanks and Regards
 >Sridhar
 >
  >>-----Original Message-----
  >>Do you get any problems with POST method if JRUN is not
 >active? If so, this
  >>is a JRUN issue.
  >>
  >>--
  >>//David
  >>IIS
  >>This posting is provided "AS IS" with no warranties, and
 >confers no rights.
  >>//
  >>"sridhar@emacmillan.com"
 ><anonymous RemoveThis @discussions.microsoft.com> wrote in
  >>message news:14ac01c3f261$3ae68040$3501280a@phx.gbl...
  >>Hi,
  >>
  >>We have installed Jrun4.0 in Win 2k and its running along
  >>with IIS 5.0. Presently a request to any website hosted
in
  >>the server from Netscape 7.1 in PC or IE 5.2 in Mac we
get
  >>this error "HTTP/1.1 400 Bad request".
  >>
  >>This happens only when the HTTP request uses POST method.
  >>As we are aware that JRUN gets the HTTP request and then
  >>forwards it to IIS, we feel that there could be a problem
  >>here.
  >>
  >>PS: In case there is a proxy server then this works fine,
  >>only when there is direct connection then this error
  >>results.
  >>
  >>Thanks and Regards
  >>Sridhar
  >>
  >>
  >>.
  >>
 >
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP 1.1 400 Bad request 

thanks for the detailed response. We have reinstalled IIS
and the error is gone.

thanks
sridhar


 >-----Original Message-----
 >400 Bad Request is pretty much indicative of something
wrong that the client
 >browser is doing (or a buggy ISAPI Filter that modified
the request
 >incorrectly on the server). It is rarely an issue with
the web server (web
 >server is simply telling you "I'm getting a bad
request!", so you need to
 >start looking at what's sending it the bad request and
fixing that.
 >
 >Get a NetMon network trace of the actual request that the
server received
 >and post that here.
 >
 >JRUN is something that runs on IIS and forwards request
to a Java VM to be
 >executed, so it can be a cause of the above. To be
absolutely certain, JRUN
 >CANNOT FORWARD ANYTHING TO IIS TO EXECUTE.
 >
 >For example, if you send a POST request, did it have a
Content-Length header
 >and entity body when it reached IIS? A POST request
without Content-Length
 >is an invalid request. Also, if request headers are not
terminated with
 >\r\n , that is also invalid. Etc. In all these cases,
it's a client-side
 >problem; server is merely throwing up the red flag.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"sridhar" <anonymous.TakeThisOut@discussions.microsoft.com> wrote in
message
 >news:119df01c3f5d2$2c2d7620$a301280a@phx.gbl...
 >Hi,
 >
 >Thanks for the reply. We removed ISAPI filter and also
 >uninstalled JRUN. Still getting the same error.
 >
 >Thanks and Regards
 >Sridhar
 >
  >>-----Original Message-----
  >>I'm referring to the ISAPI Filter that JRUN installs --
 >did you make sure it
  >>is still not active.
  >>
  >>My suspicion is that something on your server is
 >modifying/parsing HTTP
  >>incorrectly, causing IIS to think something is a new
 >request when it isn't,
  >>thus triggering the 400 Bad Request (Verb). ISAPI
 >Filters can do this, so I
  >>want you to disable all your ISAPI Filters. In
 >particular, I know that JRUN
  >>tries to hijack all requests from IIS, so it is a prime
 >suspect. If it does
  >>it incorrectly (for example, IE can do pipelined HTTP
 >requests (part of HTTP
  >>spec), which JRUN may be botching up), it could cause
 >this problem -- in
  >>which case this is a JRUN bug that you need to find
 >support for.
  >>
  >>--
  >>//David
  >>IIS
  >>This posting is provided "AS IS" with no warranties, and
 >confers no rights.
  >>//
  >>"Sridhar" <anonymous.TakeThisOut@discussions.microsoft.com> wrote in
 >message
  >>news:10c6901c3f3d9$bf1800e0$a601280a@phx.gbl...
  >>David, thanks for the reply. We still get the error even
  >>when JRUN service is stopped.
  >>
  >>Thanks and Regards
  >>Sridhar
  >>
   >>>-----Original Message-----
   >>>Do you get any problems with POST method if JRUN is not
  >>active? If so, this
   >>>is a JRUN issue.
   >>>
   >>>--
   >>>//David
   >>>IIS
   >>>This posting is provided "AS IS" with no warranties, and
  >>confers no rights.
   >>>//
   >>>"sridhar@emacmillan.com"
  >><anonymous.TakeThisOut@discussions.microsoft.com> wrote in
   >>>message news:14ac01c3f261$3ae68040$3501280a@phx.gbl...
   >>>Hi,
   >>>
   >>>We have installed Jrun4.0 in Win 2k and its running
along
   >>>with IIS 5.0. Presently a request to any website hosted
 >in
   >>>the server from Netscape 7.1 in PC or IE 5.2 in Mac we
 >get
   >>>this error "HTTP/1.1 400 Bad request".
   >>>
   >>>This happens only when the HTTP request uses POST
method.
   >>>As we are aware that JRUN gets the HTTP request and then
   >>>forwards it to IIS, we feel that there could be a
problem
   >>>here.
   >>>
   >>>PS: In case there is a proxy server then this works
fine,
   >>>only when there is direct connection then this error
   >>>results.
   >>>
   >>>Thanks and Regards
   >>>Sridhar
   >>>
   >>>
   >>>.
   >>>
  >>
  >>
  >>
  >>.
  >>
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP 1.1 400 Bad request