The bug is about parameters on the http uri, such as http://localhost:8080/?param=value These parameters are put in properties for non POST http requests. The problem with POST requests is that when the content type is application/x-www-form-urlencoded (which is usually the case), the content of the post request is also read to decode form parameters. This lead to error when using the stream as an xml. I think we could have both behaviors by adding a flag to control that.
You can also access the request uri which is put in a map with all cgi headers. On 8/14/06, bruce76 <[EMAIL PROTECTED]> wrote:
Hi, Does anyone know the status of SM-228? I see that HttpMarshaler will take the request and put the values in the NormalizedMessage as setProperty(). Is there any reason why the bug is still open? Thanks, Bruce -- View this message in context: http://www.nabble.com/SM-228-and-URL-parameters-tf2104691.html#a5800707 Sent from the ServiceMix - Dev forum at Nabble.com.
-- Cheers, Guillaume Nodet
