244640 - PAC: end user document proxy configuration files

Status: VERIFIED FIXED

(Documentation Graveyard :: Help Viewer, defect)

Description

[Marc Bejarano]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421

there is currently no help topic that describes how to write and use a proxy
configuration file (aka PAC file).  i thought bug 128270 was tracking this, but
apparently it was only tracking the obsolete web page.

Reproducible: Always
Steps to Reproduce:

Comment 1

[benc]

Marc: thanks for creating a new bug for this specific item.

I've got two documents in the works (trapped on a system at home)... I'll send
it to you for edits if you like, then post the draft here before cvs adding to
the web site.

Bug 142498 will be for system admins + end users that can write PAC files.

I've also got a truly end user, support-ish document in the works, which I will
post via this bug.

If there are things you want detailed, please add the appropiate comments to
either bug.

Comment 2

[benc]

I've made the first, shameful draft, and requested individual feedback. I'll be
posting the second, feedbacked, humble draft here soon.

Comment 3

[benc]

Attachment: first draft w/ some feedback

feedback in bullet points or clipped context please.

Comment 4

[benc]

benc% cvs commit enduserPAC.html 
RCS file: /cvsroot/mozilla-org/html/catalog/end-user/customizing/enduserPAC.html,v
done
Checking in enduserPAC.html;
/cvsroot/mozilla-org/html/catalog/end-user/customizing/enduserPAC.html,v  <-- 
enduserPAC.html
initial revision: 1.1

Comment 5

[benc]

Not added to index yet. Feedback please, otherwise, I'll cut loose sometime next
week.

Comment 6

[Daniel Wang]

benc, we are switching from catalog/ back to docs/. can you move the file to
docs/end-user/ ?

> browser that supports PAC, (for example, IE and Safari do too), 
remove extra comma -> browser that supports PAC (for example, ...

> use a URL, (like http://proxy/file.pac)
remove extra comma -> use a URL (like http://proxy/file.pac)

> PAC will reload anytime you change the URL or press the "reload" button. 
-> PAC reloads everytime you change the URL or press the "Reload" button in
Preferences.

> about PAC, (usually to modify or create your own file), 
remove extra comma -> about PAC (usually to modify or create your own file), 

and you should have your name on it :-)

Comment 7

[benc]

I'll make all the document changes, but I'd like to see the discussion on /docs
before moving stuff. I've been putting all my new stuff in here for years, so I
don't want to move unless it is part of a complete plan that has asa's signoff.

Comment 8

[benc]

RESOLVED/FIXED:

This is baked, as far as I can tell. The only open item to me is whether or not
a link to this bug should appear.

Daniel, can you give me a bug number or point me to some discussion about the
change to "docs"? We went away from docs -> catalog b/c docs was too flat and
not scalable. I talkd to Marcia and some other mozilla people today, and they
didn't seem to think there was an official plan.

Comment 9

[Marc Bejarano]

the original summary for this bug was "PAC: mozilla help needs to document proxy
configuration files".  i think it's great that there is an online document
describing PAC functionality for end users, but i still think that the included
help content has to have something about PAC in it, if nothing other than a
pointer to other online docs.

re-opening and changing summary from "PAC: end user document proxy configuration
files" to "PAC: mozilla help needs to document proxy auto-configuration files"

Comment 10

[benc]

Marc, please just create a second bug, do not change this bug.

I am interested in helping w/ the content of the help files, so you can cc: me.

Comment 11

[Marc Bejarano]

ok, ben.  putting this back to RESOLVED/FIXED and reverting the summary.

i opened bug 269919 to once and for all track updating the included mozilla help :)

Comment 12

[benc]

I've made some minor updates to this article, and also found a contact on support.mozilla.com, to see if a Firefox-centric version of the document could be made in the right place...

I also added the bug number, so I'm going to close this, for now.