On Sep 6, 11:15 am, Folke <[EMAIL PROTECTED]> wrote:
> On Sep 5, 3:03 pm, Rohit <[EMAIL PROTECTED]> wrote:
>
> > > Personally, I think you should let your webserver escape und unescape
> > > the \0 bytes before handing the data to your back-end application.
> > > This would make your device more robust and probably safer.
>
> > Would you elaborate more on this ? What exactly my webserver should
> > do ?
>
> Well, your HTTP service must be able to accept data that contains 0-
> bytes. The important thing is that the browser sets the Content-Length
> header to the number of bytes in the POST request which it does
> automatically. All you need to do is to go over each byte check if you
> want to escape it and then give the data to your uclibc app. (Don't
> forget to unescape before sending the data back to the browser.)
URL class seems to solve my problem. Thanks for all the help.
Rohit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
