> My brain is melting. > any help would be much appreciated. > Thanks. > --Alex
I'd recommend fiddling with trailing slashes and leading dots on the path and domain items. or prune the path all the way back, and see what's on the browser. You are working at least sometimes with a browser that allows reasonable levels of debugging with this kind of thing? I'd suggest Firefox or Mozilla, with the "ask every time" setting for cookies, *and* the LiveHTTPHeaders extension installed. http://livehttpheaders.mozdev.org/installation.html WebDeveloper extension is also incredibly helpful to me, and gives easier access to headers. http://chrispederick.com/work/firefox/webdeveloper/ Then you can see from the client side what's really being sent and received, which might be easier even than from the server side. I've often found it puzzling what would and would not get sent back, and how a browser modifies it, and how a server recognizes it. Nothing specific to your code, really, just an observation and a set of headaches I've been through and have done my best to expunge from my personal memory banks. For all I know most of my trouble was with JavaScript. But just suggesting a place to look. _______________________________________________ Boston-pm mailing list Boston-pm@mail.pm.org http://mail.pm.org/mailman/listinfo/boston-pm
