Closed Bug 96914 Opened 23 years ago Closed 23 years ago

Support customizing proxies

Categories

(CCK Graveyard :: CCK-Wizard, enhancement)

x86
Windows 95
enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bobj, Assigned: shrutiv)

Details

(Whiteboard: nsbranch+)

Attachments

(3 files)

There have been some requests to support customizing proxies.
Blocks: 96876
QA Contact: blee → jimmyu
Updating QA contact to jimmyu for half of the CCK bugs, while Bom-shik is gone.
Status: NEW → ASSIGNED
Whiteboard: nsbranch+
Whiteboard: nsbranch+ → nsbranch+ need r=
Comment on attachment 49537 [details]
Patch file for Proxy UI (this is only for thr UI)

r=tao
Whiteboard: nsbranch+ need r= → nsbranch+
Comment on attachment 49843 [details] [diff] [review]
Patch: Modified Proxy UI (this is only for the UI)

r=tao
Attachment #49843 - Attachment is patch: true
Whiteboard: nsbranch+ → nsbranch+ need r=
Comment on attachment 50027 [details] [diff] [review]
Patch: Backend for proxy customization

r=tao
Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: nsbranch+ need r= → nsbranch+
Please test choosing "Automatic proxy configuration", but leave the URL blank,
and see what the browser does.  I'm worried this might cause a problem.

(The browser Preferences allows this too, so if there is a bug in CCK,
then there is probably a bug in the browser too.  The difference is that CCK
is setting up the default behavior...)
Yes, choosing the "Automatic proxy configuration" and leaving the URL blank in
CCK cause problem with running the bits. The bit works fine with the initial
installation, but to restart the browser will not launch.
Running the same bit of sweetlou and changing the setting in Preference doesn't
have this problem. Restart the browser and it will launch and functional.


What are the posiible solutions to overcome this error when the user chooses 
manual proxy configuration and automatic proxy configuration?
Opened new bug 101658 for the auto proxy URL problem.

We should test potential error cases for the manual proxy settings too.

For manual proxies, try combinations of blank hosts, blank ports and 0 ports,
and see if they cause problems in the browser.

Shruti and I quickly looked at the browser code and we ***think*** the code
is robust and treats null string hosts or 0 ports as direct.  Not sure what
happens if the port is a null string...  (The browser prefs, seem to set the port
values to 0 if you leave the port text field blank.)
Verified CCK build 2001-10-01-09 include support for customize proxies
Status: RESOLVED → VERIFIED
No longer blocks: 96876
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: