manage_workspace Redirect exception

[Gregg Reynolds]

A "Bobo-Exception-Type: Redirect" is preventing Zope from working properly when proxied by Lighttpd, with or w/out ssl. The symptom is that only the first 3 or 4 lines of the workspace appear (for http://example.com/manage) and then the browser seems to hang. However, the same error apparently occurs when running without the proxy; the only difference is the entire page/frame draws. The LiveHTTP header log:

--------------
http://example.org:8080/manage_workspace

GET /manage_workspace HTTP/1.1
Host: example.org:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://example.org:8080/manage
Cookie: tree-s="eJzTyCkw5NLIKTDiClZ3hANXW3WuAmOuRKCECUjWFEnWuaocJGvGlQiSNkeWySwGyVgAZRIT9QAFFBcY"; _ZopeId="83902355A2vOnA5pNQA"
Authorization: Basic YWRtaW46bEA0a3cwbiM=

HTTP/1.x 302 Moved Temporarily
Server: Zope/(Zope 2.10.2-final, python 2.4.4, openbsd4) ZServer/1.1
Date: Sun, 25 Feb 2007 19:36:33 GMT
Bobo-Exception-Line: 87
Content-Length: 0
Bobo-Exception-Value: See the server error log for details
Bobo-Exception-Type: Redirect
Connection: close
Location: http://example.org:8080/manage_main
Bobo-Exception-File: Management.py

I can't see how to get the "server error log" to give me any useful details. Can anybody help me figure this out? I'd want to use lighttpd with ssl to proxy zope/plone, and it seems to work fine except for this.

Thanks,

gregg reynolds

[Gregg Reynolds (dev-mobileink)]

Sorry, forgot to mention, the Bobo exception message occurs with or without the proxy server. Try http://example.org:8080/manage_workspace and examine the HTTP headers. Same goes with VHM URLs: http://kbui.org:8080/VirtualHostBase/http/kbui.org:8080/VirtualHostRoot/manage_workspace etc. shows the same result, so I don't think it's a proxying/VHM issue.

[Andreas Jung (ajung)]

Changes: submitter email, importance (critical => medium)

[Hanno Schlichting (hannosch)]

This is a support request that should have gone to a mailing list. The error referred to those lines:

if m.find('/'):
    raise Redirect, ("%s/%s" % (REQUEST['URL1'], m))

So I guess there was a problem with a trailing slash (or a missing one) in the configuration.