On Thu, May 27, 2010 at 3:06 AM, T.J. Crowder <t...@crowdersoftware.com> wrote: > Hi, > > Sorry, I left something fairly important out of my long rambling post > earlier: You have to include the CORS response headers in *both* the > OPTIONS response *and* the GET response. E.g., in pseudocode:
Aha, I suspected as much. I didn't catch that in the spec I read but given the web's stateless behaviour my instincts told me that something like this had to be required. Confirmed that this fixes the problem. I'm seeing proper responses in the transport.responseText now. Many thanks, Mike -- Michael P. Soulier <msoul...@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
