xsltforms-support

Re: [Xsltforms-support] unexpected behavior on PUT

[Alain C. <ala...@ag...>]

The default behavior when a cross-domain request is detected is to 
generate a GET method with a callback function name.

Are you sure that the PUT submission is sent to the same domain and port??

Thank you for your feedbacks!

-Alain

Le 08/03/2012 18:54, C. M. Sperberg-McQueen a écrit :
> I'm experiencing slightly unexpected behavior with an attempt to
> save a document on a server.
>
> The Subversion repository does not show the new document, and
> the Apache logs don't show a PUT -- they show a GET, and the
> URI of the GET is the URI I was trying to PUT the document to, with
> the string  "?callback=jsoninst" appended.
>
> When I saw unexpected behavior I checked out the Subversion
> copy; the unexpected behavior persists when I use /trunk/build
> as the XSLTforms directory.
>
> I'll try to make a stripped down version of the form to make things
> very very simple for testing.  But in the meantime, any advice would
> be helpful.
>
> MIchael Sperberg-McQueen
>
>
>

Re: [Xsltforms-support] unexpected behavior on PUT

[C. M. Sperberg-M. <cm...@ac...>]

On Mar 8, 2012, at 12:05 PM, Alain Couthures wrote:

> The default behavior when a cross-domain request is detected is to generate a GET method with a callback function name.
> 
> Are you sure that the PUT submission is sent to the same domain and port??

Ah.  It could be a port difference -- I am trying to figure out when to
use http and when to use https.  I will look more carefully with particular
reference to that.  

Thank you!

>> 

Re: [Xsltforms-support] unexpected behavior on PUT

[C. M. Sperberg-M. <cm...@bl...>]

On Mar 8, 2012, at 7:57 PM, C. M. Sperberg-McQueen wrote:

> 
> On Mar 8, 2012, at 12:05 PM, Alain Couthures wrote:
> 
>> The default behavior when a cross-domain request is detected is to generate a GET method with a callback function name.
>> 
>> Are you sure that the PUT submission is sent to the same domain and port??
> 
> Ah.  It could be a port difference -- I am trying to figure out when to
> use http and when to use https.  I will look more carefully with particular
> reference to that.  
> 
> Thank you!

More systematic tests show (a) that the GET requests with callback
function names are indeed logged when there is a mismatch of some
kind between the form and the PUT request (in this case, when one is
http and the other is https), and (b) that the original cause of my problem
(the one that led me to start mucking about with things in the first
place) was that the portion of the site where the form resides, and the portion
of the site where the PUT must go (into the Subversion-backed WebDAV
server) both use HTTP Basic authentication, but used different AuthName
parameters.  So my browser was failing to use the appropriate credentials
to (re-)issue the request, and the PUT was failing with a 401.

Thank you, Alain, for your help.

MIchael



-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************