192476 - Linksys router ignores <script>

Status: RESOLVED INVALID

(Core :: Networking, defect)

Description

[Gili Tzabari]

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3b) Gecko/20030208
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3b) Gecko/20030208

I'm trying to configure my Linksys router which works fine under IE but fails
miserable under Mozilla. I traced the problem to a bug in Mozilla. See the
attached HTML code for reference.

Reproducible: Always

Steps to Reproduce:
1. When I click on the APPLY button, Mozilla's javascript console reports
"ValidDevice() is not defined"
2. Notice the top of the HTML page contains <script>Gozila.js</script> which in
turn contains the ValidDevice() definition.
3. If I hit Gozila.js manually, go back to the original HTML page and *then* hit
APPLY the page suddenly works

Comment 1

[Gili Tzabari]

Attachment: HTML page used to reproduce error

Comment 2

[Gili Tzabari]

Attachment: Gozila.js being referenced by <script>

Comment 3

[Olivier Cahagne]

JavaScript console shows:

Error: ValidDevice is not defined

Propose to move to Tech Evangelism. Which router/gateway model and brand is this ?

Comment 4

[Josh Birnbaum]

see also bug 134334 and bug 190524.

Comment 5

[Gili Tzabari]

This is a Linksys "Wireless Access Point Router with 4-Port Switch - Version 2"
(model number: BEFW11S4)

Comment 6

[Gili Tzabari]

PS: This bug was reproduced on the latest firmware version.

Comment 7

[Phil Schwartau]

Assigning to Browser-General until we can get further info.
This is not going to be a JS Engine issue.

When I save the HTML and JS files given in Comment #1 and Comment #2
locally, I do not get the error "ValidDevice() is not defined".

Gili: what happens if you try that? Do you still get the error if
you open the HTML and JS locally?

Comment 8

[Josh Birnbaum]

As long as this is in browser-general, adding some text to the summary for
cross-referencing with the other Linksys bugs.

Comment 9

[Gili Tzabari]

Confirmed: When I save the page to disk and load it from there, I don't get the
<script> bug. The only way to reproduce the problem is work directly off the device.

Comment 10

[Sean Middleditch]

On my cable/dsl router (BESR11) this also happens.  I don't get an error tho,
merely, nothing happens on *some* admin pages when I press apply.

I've emailed Linksys about this, and they seem to refuse to want to fix their
code to be anything resembling correct - they won't even test it in any
Mozilla-based browser.  They tell me to use IE or NS4.  Some Evangelism work by
more influential people than I could *definitely* be used on these people....

Comment 11

[Gili Tzabari]

I think Linksys is right, this *is* a mozilla bug as I've clearly proven above.
Maybe your case is different from my own, but in my case it is a clear-cut case
of Mozilla ignoring <script> tags. The error messages I see (and perhaps you
too) are due to the fact that mozilla does not load the <script>. As far as I
can tell, Linksys' page is correct HTML code.

Mozilla team: why there is no movement on this issue? What do we do next?

Comment 12

[Josh Birnbaum]

Sean: are you looking at Tools, Web Development, JavaScript Console?  The error
will show up there.

In general, can someone run a packet sniffer while trying this with their
Linksys?  I might be off base, but I think the question is: What is different
about connecting to the device that causes the error?  Since saving the files
and running locally seems to work just fine.

Comment 13

[Phil Schwartau]

> In general, can someone run a packet sniffer while trying this
> with their Linksys? 

Good idea; reassigning to Networking. Again, the site seems to work
when saved locally, so we'll need to trace the packets from the 
site itself. Currently the URL field for this bug is blank. Is there
a URL we can go to? Or is this stored directly on the router? 

Comment 14

[benc]

Uh, maybe a URL issue?

What is the in your screen when you load the page?

Or, maybe some HTTP issue? There is some standard troubleshooting like turn off
pipelining, etc.

Comment 15

[Darin Fisher]

Gili: can you please capture a HTTP log using the steps given here:

  http://www.mozilla.org/projects/netlib/http/http-debugging.html

thanks!!

Comment 16

[Gili Tzabari]

This is probably caused by Mozilla blocking popups. Another related issue was
found to be the result of this. And of course, copying the files locally changes
their URL which explains why it suddenly works.

Comment 17

[Phil Schwartau]

Gili: thanks. Does the problem go away if you do not block popups?
If is doesn't, try a "fresh" Mozilla profile and see if that works:

   Tools > Switch Profile > Manage Profiles > Create Profile

If the problem is due to popup blocking, we should either resolve
this bug as WORKSFORME, or resummarize and reassign it.

Comment 18

[Gili Tzabari]

Hi Phil,

   I've run some tests:

- This bug doesn't go away with a fresh profile or enabling/disabling popup
blocking.
- I followed instructions from here:  
http://www.mozilla.org/projects/netlib/http/http-debugging.html and created two
log files. In the first instance (log-works.txt) the pop up worked. In the
second instance (log-fails.txt) it did not work.

    I have no idea why the pop up worked the first time but it is not
reproducible. I tried doing the exact same thing a second time (which is when
log-fails.txt was generated) and it did not work. Perhaps this has something to
do with caching of HTML files?

     Please compare the two logs and try spotting the differences.

Thanks,
Gili

Comment 19

[Gili Tzabari]

Attachment: HTTP logs for when the page worked correctly

Comment 20

[Gili Tzabari]

Attachment: HTTP logs for when the page failed to pop up dialog

Comment 21

[Olivier Cahagne]

Gili, can you upgrade to latest firmware ?
Your comment 6 was posted ealier than latest (as of now 1.45) firmware for the
BEFW11S4 v2: http://www.linksys.com/download/vertxt/befw11s4_ver3.2.txt
[...]
2. Improved web based firmware upgrade using Netscape 7.0.

I know it's not related your particular issue but it may have side effects or
even unmentioned fixes.

Comment 22

[Gili Tzabari]

Olivier, updating the firmwire is not a good idea. If this patch does make this
problem go away we'll no longer be able to reproduce and that's a bad thing. A
bug is a bug is a bug. Until we're able to figure out the cause it would be a
bad idea to simply assume the HTML page is at fault. People shouldn't have to
hack Mozilla-workarounds to fix things.

Once we resolve this issue, I will upgrade.

Comment 23

[Olivier Cahagne]

Gili, did you try a recent Mozilla build (such as 1.4 or 1.5b) ?

I'm not seeing the JS error (using 2003082604 on Win2k) I was seeing in comment
3, probably because this was with an older build (circa 1.3).
A possible issue I see was the linefeeds in source (which breaks copy'n'paste
with Ctrl-A). 

Comment 24

[Gili Tzabari]

- I just reproduce the same bug under "Mozilla/5.0 (OS/2; U; Warp 4.5; en-US;
rv:1.4) Gecko/20030825" which is the latest I could get my hands on.

- Regarding the linefeeds you mentioned: how do we know if this is the cause?

Comment 25

[Peter Canada]

Please be advised this bug occurs in BOTH Firefox and Mozilla, I ma using a
BEFSR41 ver.2 Linksys Router.

Comment 26

[Peter Canada]

(In reply to comment #25)
> Please be advised this bug occurs in BOTH Firefox and Mozilla, I ma using a
> BEFSR41 ver.2 Linksys Router.
> 

Another note this is using linux Kernel 2.4.26, problem also reoccurs in windows
xp home.

Comment 27

[Peter Canada]

Another note sorry for the multiple posts I should have thought this through
before I posted. The bug appears to only occur in certain sections of the of
router page on the router. ie setup page.

Comment 28

[Mike Kaply [:mkaply]]

See bug 222814

for more info. We should dupe one way or the other.

This is a Linksys bug in that their router is flaky, but we know how to work
around it the way IE does.

Comment 29

[Peter Canada]

This issue appears resolved with a firmware update posted June 4,2004 (Firmware
version 1.45.11) for the Linksys BEFSR11 Routers.

Comment 30

[Darin Fisher]

-> default owner

Comment 31

[Peter Canada]

Bug 222814 or this one should probably be duped! Also I have come to believe this may be Java 1.5 JRE related as well. When running this this release series of Java I have notice the issue of not being able to click certain links to be javascript releated, but yet when I install Java 6 or Java 7 alpha/betas this issue does not occur. These are all javascript run pages, that this occurs on. I don't protest to know anything about web page javascript coding and Java, but it appears this issue may be Javascript and Java interrelated. Also possibly due to bad javascript coding.

Comment 33

[Matthias Versen [:Matti]]

Is this still a problem ?
This looks like a bug in the routers firmware