Bug 41 - Bugzilla cookies should have PATH=/bugzilla/ instead of PATH=/
Summary: Bugzilla cookies should have PATH=/bugzilla/ instead of PATH=/
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
(Show other bugs)
Version: 2.1r
Hardware: All Linux
low
low vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1998-11-11 13:35 UTC by Aleksey Nogin
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-12-07 17:10:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Aleksey Nogin 1998-11-11 13:35:28 UTC 
Hi,

Currently Bugzilla sets cookie path to / :

Set-Cookie: Bugzilla_login=ayn2@cornell.edu ; path=/;
expires=Sun, 30-Jun-2029 00:00:00 GMT

As a result, browser sends cookies with all requests for
pages on developer.redhat.com which makes those pages
uncacheble in HTTP caching servers (such as Squid).

I believe it would be better to use "path=/bugzilla/"
Comment 1 Need Real Name 1998-11-11 19:37:59 UTC 
Talked to Terry, and this is something that should be fixed.
It will have to wait until after the code merge, though.
Comment 2 Need Real Name 1998-12-08 01:11:59 UTC 
this has been hard-coded for now, will be cleaned up later.
Comment 3 Aleksey Nogin 1999-11-21 19:57:59 UTC 
This is a problem again in the new version of Bugzilla
Comment 4 David Lawrence 1999-11-22 19:55:59 UTC 
Ok, I need to change this back. I admit that there a lot of nick picks that did
not get into the new bugzilla code. But with all you guys help, I am sure I will
eventually get them all.
Comment 5 David Lawrence 1999-12-07 17:10:59 UTC 
Ok this is fixed now, sorry for the delay :)
Note You need to log in before you can comment on or make changes to this bug.