Closed
Bug 129045
Opened 22 years ago
Closed 19 years ago
SOCKS4 support is broken on RS6000-AIX
Categories
(Core :: Networking, defect)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: kenshir, Assigned: darin.moz)
References
()
Details
Attachments
(1 file)
68.76 KB,
image/jpeg
|
Details |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; AIX 002474094C00; en-US; rv:0.9.5) Gecko/20011024 BuildID: 2002020605 When configuring mozilla to use a SOCKS4 proxy under powerpc-ibm-aix4.3.3, the proxy layer is apparently attempting to use the socks4 host as an HTTP proxy host. My socks4 host is returning an error message indicating the browser is making a proxy request, which it cannot serve. It is important to note that the 0.9.5 release did work correctly on this platform for socks4 functionality. Beginning with the 0.9.6 release, and under all subsequent releases including the present 0.9.8 release, this functionality has not worked. Reproducible: Always Steps to Reproduce: 1.Under Edit->Preferences->Advanced->Proxies->Manual proxy configuration put a valid socks4 host in the line (socks2.server.ibm.com for me). 2.Click OK 3.Go to any web address Actual Results: socks4 proxy returns an error message coded in HTML. This message says that the browser tried to make a request as if the host was an HTTP proxy, which it is not. The socks4 server refuses all such requests. Expected Results: Load web page accordingly. The HTML message of the socks4 server is : <html><head><title>Configuration Error</title></head> <body> <h1>This machine is not an HTTP proxy</h1> <p> Please check your proxy configuration settings. This machine is a SOCKS server, and your web client attempted to use it as as an HTTP proxy server. </p> </body></html> I have a screen capture of my configuration window showing my proxy configuration. Since I can't attach it with this web form, I will be happy to email it to anyone interested in fixing this bug. Please contact me at <SPAMkenshir@MEus.ibm.comNOT>.
Comment 1•22 years ago
|
||
You can attach the attachment once you've created the bug. If you have an http proxy set, mozilla will prefer to use that rather than the socks host (this is different to ns4) check that thats not what is happening.
Reporter | ||
Comment 2•22 years ago
|
||
Bradley, I am fairly certain that I am leaving the HTTP proxy field blank (see pic). I don't know how to read the config information that Mozilla saves in the user directories, so I don't know if it would be buried in there somewhere. I am assuming though that it would show up in this dialog though if it were getting set somehow.
Comment 3•22 years ago
|
||
Odd. Does this work on linux/windows/mac builds? Can you try a newer build, too? Although I don't think anything changed in that regard recently.
Temporarily "futuring" all PAC&SOCKS bugs to clear new-networking queue. I will review later. (I promise) If you object, and can make a case for a mozilla 1.0 fix, please reset milestone to "--" or email me.
Target Milestone: --- → Future
Comment 5•22 years ago
|
||
I've been trying to get SOCKS4 support working in both Windows and Linux, and as of the latest milestone (Mozilla 1.0) this is STILL broken. I have tried with two separate SOCKS4 servers. One is windsock, which is a Java-based SOCKS4/SOCKS5 proxy server (you can find it by searching on http://freshmeat.net), and the other one is a home-brewed SOCKS4 server that I wrote to monitor my network traffic. Both servers work correctly with Internet Explorer on Windows and AIM on Windows and Linux.
Another reason we need to get contributors to check Win/Mac/Linux when smaller platforms report problems... sigh... I'll look into this Monday.
Comment 7•22 years ago
|
||
Going ahead and marking this NEW...no one i know around here has an RS6000..though if ibm were to donate one to me I would sure as heck help out the testing :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 8•22 years ago
|
||
Socks is now broken on both IRIX and Mac OS X with build 2003012213. I confirmed that it still works for mozilla 1.3a on IRIX and using netscape on IRIX. This is a serious bug, since I can no longer read email from any of the email accounts external to our company (eg mac.com). Unlike this bug, I have only seen this problem within the last few weeks. I update mozilla most days. Max.
Assignee | ||
Comment 9•22 years ago
|
||
build 2003012213 is a very broken build. please try a more recent build such as one from today or later. thx!
Assignee: new-network-bugs → darin
Comment 10•22 years ago
|
||
> build 2003012213 is a very broken build. please try a more recent build such as > one from today or later. thx! I just downloaded it this morning using this link : http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-macosX-trunk.smi.bin and it gave me 2003012213. I just tried to download directly from the web site, and the link fails. Can you provide me a valid URL to download a more recent build from? Looking in the directory, that file does not exist...I do see a mozilla-macosX-cfm.smi.bin though. Should I be downloading that now? I'll give it a try. If it is some new version, could you have the link fixed on the main page : http://www.mozilla.org/ Thanks. Max.
Comment 11•22 years ago
|
||
mozilla-macosX-cfm.smi.bin is also 2003012213...(and doesn't work) What's going on? Is noone building a Mac OS X binary any more? Max.
Assignee | ||
Comment 12•22 years ago
|
||
max: the "problem" is that mozilla has switched from the CFM binary format to the Mach-O binary format. you should download the one named MacMozilla-MachO.dmg.gz. i imagine you're not the only one still downloading the old build :(
Comment 13•22 years ago
|
||
FYI: We got already hit by that in other bugs: see also bug 191203
Comment 14•22 years ago
|
||
MacMozilla-MachO.dmg.gz works. Sorry for the noise, though I recommend someone switch the link on mozilla.org, or at least have it point to something rather than dangle. Nothing should be allowed to dangle like that :) Max.
Comment 15•19 years ago
|
||
I have tested this against the IBM socks server shown in the proxy config window with today's daily build (20040203). I went in preferences to Advanced->Proxies, clicked the Advanced button, and filled in the socks server and port at the bottom. I checked the nspr log to ensure that it was using the socks server to connect. I don't see any issues on AIX any more. Resolving this bug as WORKSFORME.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•