Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75886 --- shadow/75886 2005-09-09 12:33:53.000000000 -0400 +++ shadow/75886.tmp.14192 2005-09-12 05:06:40.000000000 -0400 @@ -297,6 +297,46 @@ Regards Yngve Zackrisson. + +------- Additional Comments From [EMAIL PROTECTED] 2005-09-12 05:06 ------- +Continuation of : +(1) I think I have found the source to the: + +'400 : Bad request' + +In Mono:s System.Runtime.Remoting.Channels.Http, +source HttpServer.cs, method ReqMessageParser.IsCustomHeader(...) +the (\\s*:\\s*) par of the regular expression +"^(?<header>\\S+)(\\s*:\\s*)(?<field>\\S+(\\s|\\S)*\\S)(\\s*)" +indicates that my custom header should be in the form of: + +sc:TransactionType 10 + +When I change my SercureChannel.dll to this naming format +no invokation got through from my Win32 MS.NET client +to my Linux Mono server application. +I used trace=System.Runtime.Remoting on the mono side. + +When changing back to the form: + +sc_TransactionType 10 + +I got trace on the Mono server but the above error, +resulting in '400 : Bad reguest'. + +Hence, to get interoperability with Win32 MS.NET +Custom Header Naming conventions the regular expression +under ReqMessageParser.IsCustomHeader(...) +probably should be changed to : + +"^(?<header>\\S+)(\\s*_\\s*)(?<field>\\S+(\\s|\\S)*\\S)(\\s*)" + +Could anyone fix this?. + +Regards: + +Yngve Zackrisson. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
