[Mono-dev] patch for remoting exceptions bug 77647

Roei Erez roeie at mainsoft.com
Thu Mar 2 04:48:12 EST 2006


Hi, 
This bug is about the differences between MS.NET and Mono regarding the
Http status codes returned in remoting using Http channel.
When an exception is thrown at the server side, during the remote
invocation, MS.NET return status code 500, which is 'internal server
error', while on Mono platform the code returned is 400, which is 'bad
request'.
These differences are not only semantic because The type of exception
that the user (client) will get is determined by these codes.
On MS.NET the status code 500 indicates to throw the exception that is
included in the response, while status code 400 causes MS.NET to throw a
System.Net.WebException.
I attached a proposed patch that makes mono compatible with .NET on
these codes, and by that makes the correct exception propagate to the
client on remote invocation.
if no one reject, I will commit
.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060302/826c018e/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: monoRemotingPatch.patch
Type: application/octet-stream
Size: 2551 bytes
Desc: monoRemotingPatch.patch
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060302/826c018e/attachment.obj 


More information about the Mono-devel-list mailing list