Closed Bug 327241 Opened 18 years ago Closed 18 years ago

Inconsistent handling of jar: (and similar?) URIs in the security manager

Categories

(Core :: Security: CAPS, defect)

Product:
Core
Component:
Security: CAPS
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

nsScriptSecurityManager::LookupPolicy doesn't use the same method as nsScriptSecurityManager::SecurityCompareURIs to deal with jar: URIs.  SecurityCompareURIs does the same thing as GetBaseURIScheme, but the latter also does things with view-source: URIs; not sure why it needs to or why other places do not need to.

Part of the problem is that LookupPolicy is rather performance-critical, so the QI-and-call-XPCOM-getter jar: thing used by the other methods may not be a good fit here...  But I'm still not that happy about the inconsistency.
Depends on: 336303
Bug 334407 resolved part of this; bug 336303 should resolve the rest.
Depends on: 334407
Fixed.
Assignee: dveditz → bzbarsky
And even resolving!
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
QA Contact: caps
You need to log in before you can comment on or make changes to this bug.