Thanks very much for the added detail. I filed an issue on the Github project
for the Python server, and within hours another Githubber had posted a pull
request fixing the bug. The server was just not aware of what to do if it got
such an OPTIONS request, so it was falling over.
Walter
On Apr
>
> It seems to be an issue on their server (BaseHTTP/0.3 Python/2.7.1+
> according to FireBug). I'll file a bug and see what happens.
>
XHR without setRequestHeader sends usual 'GET' request:
Request URL: http://zip.elevenbasetwo.com/?zip=a
Request Method: GET
Status Code: 404 Not Found
*Reques
On Apr 12, 2012, at 12:14 PM, Victor wrote:
> Same browser (Safari.latest) on the same computer, the Prototype method gives
> me a security failure (Origin [my host] is not allowed by
> Access-Control-Allow-Origin.) while the long-hand XHR (inside a Prototype
> observer) just works without any
I understand the SOP, I was wondering why it worked when I violated SOP from a
hard-coded XHR request. Under the hood, it is my understanding that Prototype
sets up a very similar XHR request anyway. It doesn't make any sense that the
one would work while the other did not. This server is specif
Hate to butt in here but did try setting an
alert(ajax.transport.responseText) right after your ajax call?
On Sun, Jun 12, 2011 at 6:28 PM, T.J. Crowder wrote:
> Hi,
>
> > As I said in my post, the Ajax.Request call are in a HTML Application
> > (HTA). Which is not a server page. It run on client
Yes, it was populated above with some complex JSON string. Thanks!
On Thu, Mar 18, 2010 at 9:16 AM, disccomp wrote:
> I think:
> requestHeaders: ['Accept-Encoding', '']
>
> should be:
> requestHeaders: {'Accept-Encoding': ''}
>
> 'msg' is not explicitly defined in your post, it is set somewhere
!
Alex Mcauley
http://www.thevacancymarket.com
- Original Message -
From: "Walter Lee Davis"
To:
Sent: Tuesday, December 22, 2009 3:54 PM
Subject: Re: [Proto-Scripty] Re: Ajax.Request
> This is an important thing to work on. If I know I will be using
> onError on the cli
This is an important thing to work on. If I know I will be using
onError on the client side, I make sure that my Ajax endpoint on the
server will return a "real" error header using PHP's header() method.
You can also get very fancy with different error header codes, too,
throwing a distinctl
If i recall correctly ...
Failure only gets called on a server error ... like a 404 ...
The failure may be due to a javascript error and would not return the alert
if that was the case.
On the back success only calls when the server has responded...
Ergo there are many things that can go
