I suspect it is one of the following issues:

1) something to do with UTF8:

http://forum.springsource.org/archive/index.php/t-39200.html

2)  Prototype does not understand HTTP/1.1 chunked-encoding. I tried
this:

$ curl 
http://67.192.186.216:8000/spinup_v1_1/api/group_unassigned/2009/10/20/12/00/2
--head
HTTP/1.1 200 OK
Set-Cookie:  session_id_spinup_v1_1=69-38-186-150-8b7cb5af-8ef3-4b61-
a307-01208ddb6b97; Path=/
Expires: Wed, 14 Oct 2009 14:40:34 GMT
Content-Type: text/html; charset=UTF-8
Pragma: no-cache
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-
check=0
Transfer-Encoding: chunked
Date: Wed, 14 Oct 2009 14:40:34 GMT
Server: CherryPy/3.1.0beta3 WSGI Server

Can you try whether the rails server also does chunked encoding or
follows HTTP/1.0 instead?

Can you force prototype to use HTTP/1.0?

Massimo




On Oct 14, 7:40 am, mdipierro <[email protected]> wrote:
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to