Hi, no, the GET requests have nothing to do with it! The POST thing fails and it returns 403! Look at the screenshot: the GET goes to stat.json which returns 200 - that is a completely different request that was created and completed half a minute before in some other part of my qx app.
The code below creates a POST to mkdir.json. Here's the server's log: [27/Feb/2010 18:48:12] "GET /fs/stat.json/joerg?nocache=1267292892074 HTTP/1.1" 200 703 [27/Feb/2010 18:48:18] "GET /fs/stat.json/joerg/Test% 20Subdir?nocache=1267292898393 HTTP/1.1" 200 1293 [27/Feb/2010 18:48:37] "POST /fs/mkdir.json/joerg/Test% 20Subdir?nocache=1267292916847 HTTP/1.1" 403 26 Jörg Am Samstag, den 27.02.2010, 13:20 -0500 schrieb Derrell Lipman: > On Sat, Feb 27, 2010 at 13:06, Jörg Sawatzki <[email protected]> > wrote: > Hi, > > I am sorry that I cannot stay in the thread but somehow the > mail > delivery was disabled because some messages bounced back to > sourceforge. > > Anyway, I have made a screenshot as well: > > http://www.einsamerplanet.de/screen.png > > Great. This has some relevant information. If you look at what's being > shown there, the final GET request got a 200 OK response (shown at the > end of the line). I'm not sure what that following error is or where > it's coming from, but it's from some class called TestS* which isn't > in qooxdoo. I suspect that your server is returning a valid (200) > response with some kind of a 403 FORBIDDEN message inside of it, or > some such thing. > > You can look at additional detail of the GET request by clicking on > the expand (+) icon of that GET request line in Firebug. You'll likely > have three tabs, Headers, Response, and Cache, and you can look at the > Response tab to see what data is actually being returned with the 200 > OK. > > Derrell > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
