Bug 18164 - Realm Authentication broken for subdirectories
Summary: Realm Authentication broken for subdirectories
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-27 15:25 PDT by Richard Berg
Modified: 2010-07-12 15:33 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Berg 2008-03-27 15:25:24 PDT
THIS IS A PROBLEM FOR 525 and 526 builds under 10.5 only; the problem does not manifest itself under 10.4

I use lasso (currently sold by lassosoft) to interface a Filemaker database to an Apache webserver. I use realm authentication and pass parameters along with web pages to ensure that users have logged in correctly. This has worked, until now, with every browser and every OS that my users utilize.

But Safari 3.1 and the latest nightly build breaks under OSX 10.5 (but not OSX 10.4). The issue comes up in the following context. Users log into a page at intranet.myspace.com/enter.lasso where they are asked to go through realm authentication. I pass lasso parameters from page to page to check that they have logged in correctly or they get bounced back to the enter.lasso page to re-login.

Under 3.1/10.5 the realm authentication works for other pages in the same directory (in my case the root directory). So if the user is send (by hitting a link) to a page at http://intranet.myspace.com/hello.lasso or http://intranet.myspace.com/search.lasso, everything works okay. If it they are sent to a different directory on the same server (say http://intranet.myspace.com/newdirectory/hello.lasso), then the realm authentication breaks (in lasso the parameters of a user name, for example, come back as blanks). My pages trap this and ask them to re-login. 

I have hundreds of pages and I am not interested in rewriting my solution to only use the root directory because of this bug. Thankfully other browsers okay and all browser work okay in 10.4.

Only the combination of 3.1 and 10.5 is the culprit. This problem does not manifest itself in Safari 3.1/10.4 or in Firefox for either 10.4 or 10.5 or in Shiira for either 10.4 or 10.5.
Comment 1 Alexey Proskuryakov 2008-12-10 23:51:04 PST
Is there any way for us to reproduce this? This doesn't look like a common problem at all.
Comment 2 Alexey Proskuryakov 2010-07-12 15:33:58 PDT
No answer, marking as invalid. Also, there were some fixes in this area in Safari 5.