On Thursday, April 11, 2013 7:17:21 PM UTC+2, Seray Uzgur wrote:
Hi, i am facing with the same thing. I know its old but i wonderred if you
found and solution?
This looks like CORS http://www.w3.org/TR/cors/
When you do a cross-origin POST (which is a simple method in the CORS
spec), then
Hi, i am facing with the same thing. I know its old but i wonderred if you
found and solution?
21 Ekim 2010 Perşembe 19:51:15 UTC+3 tarihinde Márcio Menezes yazdı:
BTW... Browser Firefox 3.6
2010/10/21 Márcio Menezes marci...@gmail.com javascript:
Ok... but it happens with ANY header. Even
Hi!.
Why does everytime I try to send a POST through RequestBuilder class and if
I add some header into it, the method goes as an OPTIONS, instead of post?
Has anyone experienced this? How can I work around it?
Regards,
Marcio
--
You received this message because you are subscribed to the
POST values should be encoded in the request data string, not the headers.
Not sure why there isn't an addPostValue method too. Here's some code I used
recently:
class CustomPOSTBuilder extends RequestBuilder {
private String request = ;
public CustomPOSTBuilder(String url,
On Oct 21, 4:59 pm, Márcio Menezes marcio@gmail.com wrote:
Hi!.
Why does everytime I try to send a POST through RequestBuilder class and if
I add some header into it, the method goes as an OPTIONS, instead of post?
Has anyone experienced this? How can I work around it?
See
Code I posted was for if you aren't using a GWT server
On Thu, Oct 21, 2010 at 11:03 AM, marius.andreiana
marius.andrei...@gmail.com wrote:
On Oct 21, 4:59 pm, Márcio Menezes marcio@gmail.com wrote:
Hi!.
Why does everytime I try to send a POST through RequestBuilder class and
if
I
Ok... but it happens with ANY header. Even if I add Content-Type,
application/x-www-form-urlencoded, as you suggested, it sends an OPTIONS
method, instead of POST.
On Thu, Oct 21, 2010 at 4:46 PM, Brett Thomas brettptho...@gmail.comwrote:
POST values should be encoded in the request data
BTW... Browser Firefox 3.6
2010/10/21 Márcio Menezes marcio@gmail.com
Ok... but it happens with ANY header. Even if I add Content-Type,
application/x-www-form-urlencoded, as you suggested, it sends an OPTIONS
method, instead of POST.
On Thu, Oct 21, 2010 at 4:46 PM, Brett Thomas
