From: Dave <dwa...@de...> - 2000-08-31 23:20:48
|
Sorry I haven't been keeping up too well lately, but what is the purpose of the WK_URI stuff in modpHandler? The handler works fine if I comment-out all of the WK_URI stuff, but if I leave it in, URLs with query parameters stop working. It seems that WebKit is trying to translate the URL into a filename without stripping the parameters. Dave. |
From: Jay L. <js...@mi...> - 2000-08-31 23:31:19
|
Sorry. I was testin that out and it must've gotten committed by mistake. Jay Dave wrote: > > Sorry I haven't been keeping up too well lately, but what is the purpose > of the WK_URI stuff in modpHandler? > The handler works fine if I comment-out all of the WK_URI stuff, but if > I leave it in, URLs with query parameters stop working. It seems that > WebKit is trying to translate the URL into a filename without stripping > the parameters. > > Dave. > > _______________________________________________ > Webware-discuss mailing list > Web...@li... > http://lists.sourceforge.net/mailman/listinfo/webware-discuss |
From: Jay L. <js...@mi...> - 2000-08-31 23:37:38
|
I spoke too soon. It should be fine right now. THe reason WK_URI is needed is because if you try to retrieve the root file, ie: "http://localhost/PATH-YOU-SET-UP/" it won't work. I had that problem with parameters, and fixed it. I thought. Would you make sure you have the most recent modpHandler and Application? Jay Dave wrote: > > Sorry I haven't been keeping up too well lately, but what is the purpose > of the WK_URI stuff in modpHandler? > The handler works fine if I comment-out all of the WK_URI stuff, but if > I leave it in, URLs with query parameters stop working. It seems that > WebKit is trying to translate the URL into a filename without stripping > the parameters. > > Dave. > > _______________________________________________ > Webware-discuss mailing list > Web...@li... > http://lists.sourceforge.net/mailman/listinfo/webware-discuss |
From: Dave <dwa...@de...> - 2000-09-01 00:09:57
|
Jay, Just to be sure I deleted modpHandler.py and did 'cvs update -dPA' just now With the unmodified file I get a KeyError since SCRIPT_URL doesn't exist in the env dict that apache.build_cgi_env returns (perhaps this is a bug in mod_python?) If I comment out the SCRIPT_URL line and uncomment the REQUEST_URI line, I'm in business again. Except if I try to access a link with parameters I get this: Traceback (most recent call last): File "Application.py", line 282, in dispatchRequest self.handleGoodURL(transaction) File "Application.py", line 373, in handleGoodURL self.createServletInTransaction(transaction) File "Application.py", line 653, in createServletInTransaction cache = { File "/usr/local/lib/python2.0/posixpath.py", line 144, in getmtime st = os.stat(filename) OSError: [Errno 2] No such file or directory: 'Examples/slist/Main.py?action=displayAddItem' The same link without the params works just fine. Now, if I comment out all of the WK_URI stuff, all is fine, except that as you say I cannot access any directory URLs. I get a Moved Permanently message with appended '/' that also don't work. Even with the WK_URI stuff, if I enter a directory URL (as opposed to a specific file) I get a Moved Permanently message unless I includes a trailing '/' Dave. Jay Love wrote: > I spoke too soon. It should be fine right now. THe reason WK_URI is > needed is because if you try to retrieve the root file, ie: > "http://localhost/PATH-YOU-SET-UP/" it won't work. > > I had that problem with parameters, and fixed it. I thought. Would you > make sure you have the most recent modpHandler and Application? > |
From: Jay L. <js...@mi...> - 2000-09-01 00:21:41
|
Dave wrote: > > Jay, > > Just to be sure I deleted modpHandler.py and did 'cvs update -dPA' just now > > With the unmodified file I get a KeyError since SCRIPT_URL doesn't exist in > the env dict that apache.build_cgi_env returns (perhaps this is a bug in > mod_python?) It exists in mine. Huh. That's the key. What version of modPython are you using? Jay |
From: Dave <dwa...@de...> - 2000-09-01 01:29:35
|
I was using mod_python 2.4 but I just upgraded to 2.4.1 (latest) with no diference. In fact, I think these variables may be coming out of Apache unless you have an older verison of mod_python that was creating it somehow. I'm using Apache 1.3.12 what versions of Apache and mod_python are you working with? I assume that SCRIPT_URL is very similar to REQUEST_URI without the params? There's also another python-embedding module: mod_snake that might be worth a looksee. It claims to support Apache 1.3 and 2.0. Dave. Jay Love wrote: > Dave wrote: > > > With the unmodified file I get a KeyError since SCRIPT_URL doesn't exist in > > the env dict that apache.build_cgi_env returns (perhaps this is a bug in > > mod_python?) > > It exists in mine. Huh. That's the key. What version of modPython are > you using? |
From: Dave <dwa...@de...> - 2000-09-02 16:39:40
|
Jay, The oddest thing, it seems that in apache 1.2.12 (not sure about earlier versions) SCRIPT_URI and SCRIPT_URL are not placed in the environment unless the mod_rewrite engine is on. Placing the following toplevel directive in my http.conf fixed the problem: RewriteEngine on Dave. Jay Love wrote: > Dave wrote: > > > > Jay, > > > > Just to be sure I deleted modpHandler.py and did 'cvs update -dPA' just now > > > > With the unmodified file I get a KeyError since SCRIPT_URL doesn't exist in > > the env dict that apache.build_cgi_env returns (perhaps this is a bug in > > mod_python?) > > It exists in mine. Huh. That's the key. What version of modPython are > you using? > > Jay |
From: Jay L. <js...@mi...> - 2000-09-03 03:25:39
|
Dave wrote: > Jay, > > The oddest thing, it seems that in apache 1.2.12 (not sure about earlier > versions) SCRIPT_URI and SCRIPT_URL are not placed in the environment unless the > mod_rewrite engine is on. Placing the following toplevel directive in my > http.conf fixed the problem: > > RewriteEngine on OK. Clearly we can't count on SCRIPT_URL/SCRIPT_URI. We'll just have to parse REQUEST_URI in modpHandler. No huge deal, just not as clean as I would like. Jay > > > Dave. > > Jay Love wrote: > > > Dave wrote: > > > > > > Jay, > > > > > > Just to be sure I deleted modpHandler.py and did 'cvs update -dPA' just now > > > > > > With the unmodified file I get a KeyError since SCRIPT_URL doesn't exist in > > > the env dict that apache.build_cgi_env returns (perhaps this is a bug in > > > mod_python?) > > > > It exists in mine. Huh. That's the key. What version of modPython are > > you using? > > > > Jay |
From: Jay L. <js...@mi...> - 2000-09-03 03:40:04
|
Jay Love wrote: > Dave wrote: > > > Jay, > > > > The oddest thing, it seems that in apache 1.2.12 (not sure about earlier > > versions) SCRIPT_URI and SCRIPT_URL are not placed in the environment unless the > > mod_rewrite engine is on. Placing the following toplevel directive in my > > http.conf fixed the problem: > > > > RewriteEngine on > > OK. Clearly we can't count on SCRIPT_URL/SCRIPT_URI. We'll just have to parse > REQUEST_URI in modpHandler. No huge deal, just not as clean as I would like. > > Jay OK, I've committed a new fix. Try it out. |
From: Dave <dwa...@de...> - 2000-09-03 20:51:45
|
Jay, I placed a patch on the SF patch manager for modpHandler.py. The current version mostly worked, but attempts to access the root without a trailing '/' were not being redirected, causing relative links to fail. Also, redirects were not being processed automatically. Both should be working correctly now. Dave. |