[Mono-dev] 400 bad request when forwarding to xsp
Carlos Solorzano
carlos at applianz.com
Sat May 6 04:48:21 EDT 2006
I have XSP running on a machine behind a firewall/router. I have the
XSP port forwarded.
I have web pages and web services.
When calling from the LAN, webservices work and web pages work, all
being called with a web browser or .net code.
When calling from the outside world web pages appear to work fine but
some web services do not work. The web services fail with a 400 bad
request WebException when calling from .net code and when calling
from a web browser I just get "Error: ConnectFailure". This only
happens if coming from outside the LAN through the port forward.
Also the web browser only fails to make the webservice call using
POST as the method, if it uses GET as the method then the webservice
works just fine.
I have reproduced this on mono/xsp 1.1.10 and 1.1.13, I have yet to
try it on 1.1.15
The error I get on code is:
Exception: System.Net.WebException
Message: The request failed with HTTP status 400: Bad Request.
Source: System.Web.Services
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse
(SoapClientMessage message, WebResponse response, Stream
responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
(String methodName, Object[] parameters)
I tried reading the response stream and got:
Exception: System.Net.WebException
Message: The request was aborted: The connection was closed
unexpectedly.
Source: System
at System.Net.ConnectStream.BeginRead(Byte[] buffer, Int32
offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset,
Int32 size)
at System.IO.Stream.ReadByte()
Anyone else seen this?
--Carlos
More information about the Mono-devel-list
mailing list