There is a problem with authentication and frames

RESOLVED INCOMPLETE

Status

()

Core
Networking
--
major
RESOLVED INCOMPLETE
16 years ago
6 years ago

People

(Reporter: Chris Beaumont, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
When using the Zope management interface, on Linux, Windows and Macintosh OS9
platforms, I am unable to bring up the 'directory' view in Zope frames, as I can
with all other browsers. This is a show-stoper for me because it means I cant
use Mozilla to manage my Zope. I suspect it is some kind of problem with
authentication.This is also a problem with Netscape 6.x and it has been manifest
for a long time. I was hoping that it would have been fixed with 1.0.

If someone is working on fixing this, and needs an example Zope to verify the
problem, I will set up an account for them on a Zope site I manage. I can be
contacted at any time at 'chris@ncafe.com'

Clearly, this is some kind of non-standard problem with authentication and I
would very much like to see it solved. I am sure that it is also causing
problems with some other web applications. Any non-standard behavior does
somewhere.

***Thank you!***


Other than this problem, (and one other which I may also report) Mozilla rules..

Chris

Comment 1

15 years ago
According to this link, Mozilla insists on case-sensitivity when
processing the string "Basic" with regards to authentication.

http://lists.zope.org/pipermail/zope-mozilla/2000-June/000328.html

The writer asserts that the string "Basic" should be handled 
to be case-insensitive, as specified in the RFC.

Comment 2

15 years ago
Here's the RFC.  

http://www.ietf.org/rfc/rfc2617.txt

The assertion of case-insensitivity is in section 1.2

1.2 Access Authentication Framework

   HTTP provides a simple challenge-response authentication mechanism
   that MAY be used by a server to challenge a client request and by a
   client to provide authentication information. It uses an extensible,
   case-insensitive token to identify the authentication scheme,
   followed by a comma-separated list of attribute-value pairs which
   carry the parameters necessary for achieving authentication via that
   scheme.

      auth-scheme    = token
      auth-param     = token "=" ( token | quoted-string )

Comment 3

15 years ago
->NEW ->component Networking: HTTP

This looks like a dupe of Bug 42008, but that was fixed 2000-06-27 (a long time
ago). Is this a regression?
Assignee: Matti → darin
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking: HTTP
Ever confirmed: true
QA Contact: imajes-qa → httpqa
(Reporter)

Comment 4

15 years ago
If anybody wants screenshots of the behavior, I'd be glad to supply. 

I recently switched to Mac OS-X on my work computer, installing a fresh copy of
Mozilla 1.1.

Strangely, Mozilla's default behavior under OS-X was okay with the Zope
management interface when first installed, but soon, without my changing
practically any preferences, (except for setting up mozilla's email) it changed
to the behavior I see on the other platforms. That may be a clue. It may simply
be a bug in the way Mozilla handles authentication after it has been
personalized in some way..

Or maybe it has something to do with cookies.. In any case, all the other
browsers with different codebases (Netscape 4.7.9, Opera, Internet Exploiter)
behave differently..

I will put a set of screenshots showing the problem up on
http://www.ncafe.com/mozillaframeproblem

If there is a simple fix, I would like to know it.

chris at ncafe dot com

Comment 5

15 years ago
chris: are you still seeing this bug with mozilla 1.3b or any recent nightly
build?  thx!

Comment 6

12 years ago
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
no response to comment#5
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.