Closed Bug 193546 Opened 22 years ago Closed 21 years ago

The following error message occures when rv1.3b is used

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 197426

People

(Reporter: dbristle, Assigned: darin.moz)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210



When entering a secure site, It's Apache/1.3.32 server complaines. that it
cannot set the cookie.


Reproducible: Always

Steps to Reproduce:
1. Must have a password to Jones International University
2. Use Student account information to enter site
3. Go to

Actual Results:  
HTTP/1.1 200 Ok Date: Sun, 16 Feb 2003 09:40:09 GMT Server: Apache/1.3.23 (Unix)
mod_ssl/2.8.6 OpenSSL/0.9.6c Content-Language: en Content-type: text/html
Set-Cookie: online.e-ed=24.163.245.104; path=/; expires=Mon, 17 Feb 2003
09:40:09 GMT; domain=.e-education.com X-Cache: MISS from e-web-3b Keep-Alive:
timeout=15 Connection: Keep-Alive Transfer-Encoding: chunked c03

Expected Results:  
Allow student information to pass

If build v1.3a or Netscape 7.01 is used, I don't have a problem.  If IE 6.0 is
used I get this error.
i don't see anything here that is security senstive.
reporter: would you please explain why you selected that box?
Component: Cookies → Networking: HTTP
otoh, I can't see any changes that would cause this bug, especially given that
it's appeared in 1.3b.

Reporter, are you able to generate a cookie log, to show the reason why it
wasn't set/sent?
reporter: are you saying that HTTP header info is shown in the browser window?
over one week, and no response from reporter.  clearing security sensitive flag.  

this bug looks like a bug about headers being shown in the browser window.  that
sounds very similar to bug 194642, which was just recently filed.  this bug is
probably a duplicate.
Group: security
BTW, my guess is that the reporter filed this security sensitive to "hide" the
testcase URL.  before opening this i verified that the "stateID" is no longer
valid, so there is nothing in this bug report that could be considered sensitive.

*** This bug has been marked as a duplicate of 197426 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.