User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-1.3.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-1.3.1
This problem is tested in all known to me installations of Bugzilla; Mozilla's
own bugzilla.mozilla.org, landfill.mozilla.org 2.18 (I cannot test with
bugzilla-tip as it has more severe problems), KDE's, Mandriva Linux, Gnome
Bugzilla and many others:
I'm connecting to Bugzilla through a caching Squid proxy, which is configured to
also cache pages whose URL contains a question mark (relying on proper cache
control headers from the HTTP server).
Bugzilla doesn't generate any cache control headers (see
http://www.mnot.net/cache_docs/ for an excellent tutorial on web caching for web
application authors), so many .cgi pages get cached by the proxy and cause
1) the login page is presented to the user multiple times during his session
2) there's a problem with Bugzilla attachments handling CGI script - when I
click "Create an attachment" and supply the file, content type and all required
info, then click "Submit", I have to login again (that's acceptable), and after
providing my username and password, I get an error "You didn't specify a file to
attach" (if I recall correctly). Tested with many bugzillas, even with
http://landfill.bugzilla.org 2.18 branch.
When I switch Mozilla proxy settings to direct Internet connection, ewerything
For more discussion on those bugs, see the Mandrake/Mandriva bugzilla where the
problem has been originally discovered:
Steps to Reproduce:
1. Install a Squid proxy and configure it to also cache URLs that contain a
question mark, e.g.:
acl QUERY urlpath_regex cgi-bin
no_cache deny QUERY
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
2. Configure your browser to use that proxy
3. Try working with Bugzilla, creating new bugs, attaching files etc.
When working with bugzilla, login is requested multiple times from the user, and
files cannot be attached.
After supplying a file, a login page is the next one presented, and the next is
a "You didn't specify a file to
attach" error. Because of the 2nd request - the login page - the attachment gets
"lost" between 1st (file attachment form) and 3rd request (error page).
User should be asked for login once, and it should be possible to attach files
BTW, I've just checked - the problem also exists with standard Squid
configuration (with forbidden caching of URLs containing '?'). So skip the
remark about configuring Squid to cache those.
Is this a duplicate of bug 167808?
Maybe. I'm not entirely sure that enabling cache control headers would solve the
problem - I only suspect that link between those problems. I'll mark this bug as
dependent on bug 167808.
I'm fairly positive that adding cache-control headers would fix this.
*** This bug has been marked as a duplicate of bug 167808 ***