Closed Bug 267342 Opened 20 years ago Closed 1 year ago

"pacUtils" code should be unescaped

Categories

(Core :: Networking, defect, P5)

x86
Windows XP
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: benc, Unassigned)

References

()

Details

(Keywords: good-first-bug, Whiteboard: [necko-would-take])

as I understand it, because we do:

      var mypac = pacUtils + pac;

This creates a monster pile of javascript PAC goo by mashing pacUtils and the
loaded PAC file together.

      evalInSandbox(mypac, ProxySandBox, pacURL);
      LocalFindProxyForURL=ProxySandBox.FindProxyForURL;

It would good for readability and other reasons to find a solution where
pacUtils is not escaped code in the source tree.
low-priority, patches welcome...
Severity: normal → trivial
Target Milestone: --- → Future
Also, I noticed that ebay.com uses the document.domain property. I tried setting
the codebase of my script to the value of document.domain, and also to 'http://'
+ document.domain. Neither worked.

It's difficult for me to confirm whether this bug would occur on all sites that
have document.domain since I don't have a webserver handy that I can configure
like that.

However it seems likely that this isn't coincidence.
Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---
Whiteboard: [necko-would-take][good first bug]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Keywords: good-first-bug
Whiteboard: [necko-would-take][good first bug] → [necko-would-take]
Severity: trivial → S4

I think I fixed this one in bug 1751698.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
See Also: → 1751698
You need to log in before you can comment on or make changes to this bug.