Closed Bug 267271 Opened 20 years ago Closed 9 years ago

networking validity checking

Categories

(Core :: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: benc, Unassigned)

References

Details

I've talked w/ several of the mozilla staff on and off about writing a set of
functions in javascript that do validity checking.

I noticed this was a potential problem with the pacUtils that support PAC files,
potentially bad input could cause really strange results.

I think we've historically assumed that the URL's will alwasys be parsed into
sensible values, but it doesn't mean that they always would.

The general idea is that moving pacUtils out into it's own resource + some
validity functions would also be good for other areas of the product, like in
the prefs panels, etc.
Depends on: 268619
I'm finishing off the first run of functions.

My thinking is this:

the functions will focus on validity checking, not fixup, so they will assume
that you have done any leading/trailing whitespace removal, cleanup, etc. 

In a web-based app, it might be desirable to call them with a check for a cookie
like "ipvalidation=off", so you can turn off all validity checking w/ a cookie
change, which is is easy to do via a javsacript: URL.
Depends on: 268893
Depends on: 273097
Depends on: 276474
Assignee: darin → nobody
QA Contact: benc → networking
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.