Closed
Bug 7398
Opened 25 years ago
Closed 22 years ago
javascript: Problem working with proxy?
Categories
(Core :: Networking, defect, P3)
Tracking
()
M10
People
(Reporter: m_gasslander, Assigned: gagan)
Details
I localized a bug i a javascript page. Here is a sample:
<html>
<head>
<title>Untitled Document</title>
</head>
<script language="JavaScript">
<!--
function
ref()
{
window.location.href='http://www.mozilla.org';
}
//-->
</script>
<A HREF=JavaScript:ref()> hej </A>
</html>
When I run this script and click on the link, the apprunner gives me an error
message:
The requested item could not be loaded by the proxy
a network error occured
unable to connect to server (TCP error no route to host)
Try again later
I am behind a firewall, but i have also tried this on a local apache-server,
excluding localhost from the proxy. (I cant exclude the proxy since apprunner
wont start without web-access).
The script works as it should on Netscape and IE
I have used M6 both on Windows NT and linux.
Best regards
Magnus Gasslander
|
||
Updated•25 years ago
|
Assignee: norris → gagan
Component: JavaScript → Networking Library
Summary: Javascript: window.location.href not working → Problem working with proxy?
user_pref("network.proxy.http", "worf-gw:1080");
doesn't work no more either..
Please fix this ASAP.. That way I can browse at my work and report more bugs.
|
Reporter | |
Comment 2•25 years ago
|
||
Im not sure its a proxy problem. When I click on the link in the included
script, the browser starts looking for page http:/// instead of
http://www.mozilla.org/
I tried the script without a proxy and it did not work there either. For me it
seems more like a Javascript error.
/Magnus Gasslander
Changing all Networking Library/Browser bugs to Networking-Core component for
Browser.
Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do
this in a bulk change. If this happens, I will fix. ;-)
Tried to with NEC sockCAP32 and still don't work..
8-3-99 build 13
Dammit! I have Free time at work and can't test Mozilla!
|
||
Comment 8•25 years ago
|
||
Gagan - Steve Elmer mentioned to me that the proxy configuration info really
shouldn't get stored in the user's profile, but that it should go along with
the connection information. Apparently there's some file that describes the
connection parameters (for instance, when a user has multiple ISPs), and our
proxy info should be either stored there, or stored in some way that parallels
which of those files are in use.
Cc'ing Steve so that he can give us more details.
|
||
Comment 9•25 years ago
|
||
Gagan and I discussed this and it does seem like adding a level to deal with
connections makes sense. Given that the existing behavior of autoconfig proxy
and profile proxy still need to work, we decided that the connection oriented
mechanism would have the lowest priority and would only take effect if the other
two mechanisms did not provide a value. This allows users who know what they're
doing to override the default choice based on how they're connected.
In addition to the proxy settings, we should determine what other values belong
in this group. I think the smtp server setting is one of them. Incoming mail
server is handled by the mail client's account concept. Publishing URL is the
only other value in the 4.x prefs panel that looks possibly related.
|
||
Comment 10•25 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
||
Comment 11•25 years ago
|
||
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
|
||
Comment 12•24 years ago
|
||
Was this a problem with proxy in general, or the javascript page?
I'd like to confirm the jacascript fragment was incorrect or that the URL is
retreivable via proxy.
|
|
||
Comment 13•22 years ago
|
||
REOPEN:
qa to me, this is the oldest unverified bug in Networking!
Since there is no patch or fix mention, I tested the fragment and it looks valid
(not a javascript expert, but hey, it works in Chimera). Javascript URLs were
broken at the time of this bug filing, so I'm resolving dupe.
|
|
||
Comment 14•22 years ago
|
||
this is probably the real problem.
*** This bug has been marked as a duplicate of 1646 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 22 years ago
Resolution: --- → DUPLICATE
Summary: Problem working with proxy? → javascript: Problem working with proxy?
|
|
||
Comment 15•22 years ago
|
||
VERIFIED, per #2
(what am I doing awake now? getting a glass of water. It's almost emtpy, and
this bug is almost done!)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•