OK, got the link by email. I will take a look.
On Oct 13, 10:49 pm, pharkle <[email protected]> wrote:
> Ok, forget the response code 0, this is just a Prototype default when
> the response status is undefined...
>
> >> getStatus: function() {
>
> try {
> return this.transport.status || 0;
> } catch (e) { return 0 }
> },
>
> Also, I'm not convinced the headers are responsible as I dumped them
> and passed them to curl and web2py still came back with the right
> response. Is this some freaky Prototype bug? Are you able to get a
> response from web2py via Ajax.Request? I made a little Rails endpoint
> and fired off requests at it via Ajax.Request and they returned
> correctly.
>
> Thanks for any help
> Alex
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" 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/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
