HTTP Request with no Content-Type header

2010-02-15 Thread Supun Kamburugamuva
Does HTTPCore add a content type in case there is no Content-Type header in the request message? Thanks, Supun.. -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com

Re: HTTP Request with no Content-Type header

2010-02-15 Thread Asankha C. Perera
Supun Kamburugamuva wrote: > Does HTTPCore add a content type in case there is no Content-Type > header in the request message? No, I do not think it should either cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com -

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #374

2010-02-15 Thread Apache Hudson Server
See -- Started by timer Building remotely on minerva.apache.org (Ubuntu) Updating https://svn.apache.org/repos/asf/synapse/branches/1.3 At revision 910207 no change for https:

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #375

2010-02-15 Thread Apache Hudson Server
See -- Started by timer Building remotely on minerva.apache.org (Ubuntu) Updating https://svn.apache.org/repos/asf/synapse/branches/1.3 At revision 910279 no change for https:

Re: HTTP Request with no Content-Type header

2010-02-15 Thread Ruwan Linton
I think Synapse nhttp transport defaults to application/octet-stream which will result in the message to be built as binary, I think Hiranya did some fix around this sometime back, Hiranya*?? Thanks, Ruwan * On Mon, Feb 15, 2010 at 5:22 PM, Asankha C. Perera wrote: > Supun Kamburugamuva wrote: >

Re: HTTP Request with no Content-Type header

2010-02-15 Thread Hiranya Jayathilaka
On Tue, Feb 16, 2010 at 6:24 AM, Ruwan Linton wrote: > I think Synapse nhttp transport defaults to application/octet-stream which > will result in the message to be built as binary, I think Hiranya did some > fix around this sometime back, Hiranya*?? > * Nope. That was for responses only. Thank

Re: HTTP Request with no Content-Type header

2010-02-15 Thread Hiranya Jayathilaka
BTW this is what the RFC says about this scenario: *Any HTTP/1.1 message containing an entity-body SHOULD include a > Content-Type header field defining the media type of that body. If and only > if the media type is not given by a Content-Type field, the recipient MAY > attempt to guess the media

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #377

2010-02-15 Thread Apache Hudson Server
See -- Started by timer Building remotely on minerva.apache.org (Ubuntu) Updating https://svn.apache.org/repos/asf/synapse/branches/1.3 At revision 910406 no change for https: