[Webkit-unassigned] [Bug 16172] Webkit based browsers are no longer able to properly handle form submission in the Siemens 6520 based routers used by Aliant (Canadian ISP)

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=16172





------- Comment #6 from ddkilzer at webkit.org  2007-11-30 03:41 PDT -------
(In reply to comment #5)
> Due to the nature of the issue occuring in the router's interface (and thus not
> a publicly accessible website) I saved one of the error prone pages as a
> web-archive, and uploaded it to the following:
> 
> http://www3.ns.sympatico.ca/guinness/Test/Aliant%20High-Speed%20Networking.webarchive
> 
> I then tested the web-archive to ensure that the error would still occur, and
> it did. The issue is with the back/cancel/next buttons at the bottom. The error
> only occurs when multiple buttons are present. On pages that only have one
> button, they work fine. 

Thanks for posting this!  I don't think it may be helpful without access to the
router, though.  (The webarchive never seems to finish loading after opening
it.)

> David: Unfortunately my technical knowledge is somewhat limited. The reason I
> am the one investigating this is because some friends of mine who work in the
> technical support group remember that I've used macs longer than most, and none
> of them could figure out what the problem is. They don't even have a mac system
> to test this on. As far as where the error is occuring, based upon the
> response, I believe it is an issue of Safari/Webkit submitting HTTP requests
> that the router either cannot handle, or interprets as invalid. 

Could they try testing with Safari for Windows to see if that has the same
issue?

http://www.apple.com/safari/

> The message "Form Input - Error: Invalid Submission Value" is generated by the
> router. 
> 
> Now, I realize that it is entirely possible that this error is caused by poor
> coding on the router. However, as it worked fine in webkit before v3, and still
> works fine in gecko/IE, I figured it would be worth submitting. 

Yes, we'd still like to know about it!  Thanks for submitting this bug report.

Another thing you could do is to capture the packets sent to/from the router
using a command like this from the terminal (requires you to type your password
to become Administrator):

sudo tcpdump -s 0 -w packets.tcpdump -i en0

This assumes that "en0" is the ethernet interface your Mac is using (en0 is
probably the wired ethernet port while en1 is wireless; run "ifconfig -a" and
look for the interface with a valid IP address).

It would be helpful to have one run for Safari 3 that fails, and one for
Firefox that works (from submitting the same form on the same page).  (Make
sure to rename "packets.tcpdump" in between runs.)

Also note that this command will log ALL NETWORK TRAFFIC, so don't log in to
another site while the command is running.  If you'd prefer not to post the
packet dumps on Bugzilla, let me know.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.