Closed
Bug 105636
Opened 24 years ago
Closed 24 years ago
auto charset detection causes multiple POST DATA warnings when entering form[form sub]
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 116217
Future
People
(Reporter: bloodnok, Assigned: alexsavulov)
References
()
Details
when entering innocuous data into a contest form, mozilla warns about multiple
POST DATA attempts. on other sites, a good example being amazon's wish list,
mozilla tries to create two entries. these appear to be related problems. these
problems existed with earlier builds but are much more annoying with 0.9.5...
Comment 1•24 years ago
|
||
confirming with build 2001101803 on Win2k. This is a recent regression as I
didn't have the problem with 1-week old builds.
I don't have time to look for a dup now, so leaving UNCO.
Keywords: regression
Comment 2•24 years ago
|
||
dont see it on 10-17-18 branch...
Comment 3•24 years ago
|
||
Confirming 2001101909 on Win2k.
Marking NEW, but I would think this is a dupe.
Oliver: If you find a dupe, please add me to its CC list.
(Dupe of bug 93154?)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: DUPEME
Comment 4•24 years ago
|
||
Olivier, dennis: Do either of you have OptiMoz (gestures) installed? I do, and
I'm wondering if that's related to this.
PS Olivier: Sorry about misspelling your name in that last post.
Comment 5•24 years ago
|
||
I do not have OptiMoz installed. Using build 2001101909 on Win2k.
PS: Alex, don't worry about my first name. :)
Comment 6•24 years ago
|
||
Another theory: Is anyone using a proxy? I'm using WebWasher
(http://www.webwasher.com), but that's worked fine with http/1.1 so far.
Or, maybe we could try a new profile?
Comment 7•24 years ago
|
||
Not using any proxy either.
| Assignee | ||
Updated•24 years ago
|
Summary: multiple POST DATA warnings when entering form → multiple POST DATA warnings when entering form[form sub]
Comment 11•24 years ago
|
||
Olivier Cahagne : are you sure you are not on transparent proxy?
Comment 12•24 years ago
|
||
_basic: not using transparent proxy but I'll check again at home where I'm 100%
sure I do not use any proxy.
Comment 13•24 years ago
|
||
Reproducable case:
go to http://www.cinebel.be/cgi/srch.exe?1,fr
choose a town (in the drop box right to "villes")
click on "aujourd'hui" (today).
btw about Alex's comment, this is a form without enctype.
Comment 14•24 years ago
|
||
Sorry for the spam, I found a nice reproducible testcase with this URL:
http://download.mcafee.com/eval/platform-language2.asp?l=0&prdc=27&s=HOME&o=10&zz=VirusScan&img=vscan_6x.jpg
(Click on Continue).
It doesn't need to fill in personal data, it's reproducible and it does not need
to log in anywhere. Tried with build 2001103003 on Win2k.
Comment 15•24 years ago
|
||
Gilles & Olivier: I'm now running 2001102903 (on Win2k), but with a completely
fresh profile (I deleted the entire "Profiles" directory and even registry.dat).
And, I haven't seen the problem since :-/. All of the testcases now work
"normally" for me (just my 2 cents).
Comment 16•24 years ago
|
||
Alex, you're right, now wfm using build 2001103103 on Win2k by creating a new
profile with 'mozilla -profilemanager'.
I would have never thought of that. I'll dig more to see what pref triggers the bug.
Comment 17•24 years ago
|
||
Olivier: So.. -> WFM?
FWIW, I wouldn't have thought of it either, but you'd be surprised what kind of
stuff a fresh profile can fix ;).
Comment 18•24 years ago
|
||
Marking WORKSFORME.
Reporter, if problem still occurs even when creating a new profile, please
reopen this bug report.
Alex, I was waiting for some time so that my new profile would match with my
usual profile but bug doesn't seem to trigger even though. I guess it was time
(4 months old profile) to clean my profile...
Status: NEW → RESOLVED
Closed: 24 years ago
Keywords: regression
Resolution: --- → WORKSFORME
Whiteboard: DUPEME
Comment 19•24 years ago
|
||
This problem got back with 2001111921 trunk linux (and some build before that).
Using the test case I provided in comment #13, I can reproduce it every time IF
I set char autodection to Japanese.
Comment 20•24 years ago
|
||
I meant "autodetection"
Comment 21•24 years ago
|
||
Gilles: Have you tried a fresh profile? See comment #16 for instructions on that.
Comment 22•24 years ago
|
||
I tried with a new profile and I still get the multiple warnings when charset
autodetection is set to japanese. When it is set to "off", there's no problems.
Comment 23•24 years ago
|
||
Ok, reopening.
-> Internationalisation?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 24•24 years ago
|
||
See also 104417
| Assignee | ||
Comment 25•24 years ago
|
||
Please provide a URL or reduced testcase whare it can be reproduced.
setting milestone
Target Milestone: --- → Future
Comment 26•24 years ago
|
||
Alexandru: see comment 13
I tried with autodection set to japanese -> multiple warning
Autodection set to off -> no warning, form correctly submitted.
Using 2002011003 and a fresh profile.
Comment 27•24 years ago
|
||
*** Bug 120802 has been marked as a duplicate of this bug. ***
Comment 28•24 years ago
|
||
OK, folks, I hope this will help. An easy reproducible testcase is
http://www.xe.com/ucc/
And: when creating a fresh profile, I can't reproduce it any more.
So the problem is either in a broken profile (WHEATHER the profile is broken, I
don't know, actually I don't think so, because other than that, everything is
working perfect) OR the problem could be in some file that is created later, as
you use more features of your profile.
Comment 29•24 years ago
|
||
If you add user_pref("intl.charset.detector", "zhtw_parallel_state_machine"); to
your prefs.js it will regress. I dunno wtf that preference does but mozilla
doesn't like it.
Comment 30•24 years ago
|
||
pajor@gnuyen.org: wow good! I have a similar thing. Probably you are using
something that is from Taiwan (zhtw = chinese taiwan). I have the same pref, but
it reads
user_pref("intl.charset.detector", "ko_parallel_state_machine");
and ko is standing for korean. So it must be used for something, since I am
viewing many Korean pages and am writing Korean e-mails too...
Comment 31•24 years ago
|
||
This bug is most likely dependent on bug 55583. This bug is critical because it
blocks all usability in Asian markets (even when visiting non asian websites).
Please mark this bug as higher priority.
Comment 32•24 years ago
|
||
As another easily-reproducible testcase, try http://forums.macnn.com
Attempting to log in or post a message triggers the bug. It seems that you have
to hit OK on the first dialog to post at all, but then you have to cancel the
second one or the data is posted twice.
I believe the forums at http://www.macslash.com are also showing this behavior.
Comment 33•24 years ago
|
||
I think comment http://bugzilla.mozilla.org/show_bug.cgi?id=105636#c29 gives
the crucial hint: I had the same problem and removing the following line:
user_pref("intl.charset.detector", "ja_parallel_state_machine");
from my prefs.js solved it.
What is the purpose of this line, when does it get added to the prefs.js
file, what does "ja_parallel_state_machine" mean?
And why should this cause the POSTDATA warning to appear for some
form submissions?
Updated•24 years ago
|
Blocks: profile-corrupt
Comment 34•24 years ago
|
||
"ja_parallel_state_machine" is: character coding - auto-detect - japanese (view
menu).
removing the entry equals setting this to "(off)".
doing so solved my problem on linux (currently using 0.9.9) which i described in
bug 116217 , although it is more appropriate here (sorry, searched for
"postdata" and this bug does not show up in the search results)
Comment 35•24 years ago
|
||
a few observations in light of my test with amazon.de and my inability to come
up with a testcase:
(all observations with charset-autoselect-japanese)
- loading amazon.de (any page) auto-selects charset windows-1252.
- overriding with another western charset (iso-8859-15) and then loading another
page autoselects windows-1252 again.
- manually changing charset on a page with postdata (shopping cart, remember
item(?) "auf die merkliste" and vice versa) issues a postdata warning; does not
repost, though (tested).
- toggling charset-autoselect does the same
therefore i wonder:
what conditions cause mozilla (browser) to prefer charset windows-1252 over
iso-8859-15 (my default charset)? the page itself does not specify one.
if this were related, this issue might be several checks for correct charsets to
render the page - it would at least the multiple postdata warnings.
Comment 36•24 years ago
|
||
I also have few testcases in 116217 one of them with not able to login into bank
account.
After deactivating autodetecton of Russian all works fine, so I sudgest to
change the summary to reflect this.
Comment 37•24 years ago
|
||
Okey-dokey.
Old summary:
"multiple POST DATA warnings when entering form[form sub]"
New summary:
"auto charset detection causes multiple POST DATA warnings when entering
form[form sub]"
Summary: multiple POST DATA warnings when entering form[form sub] → auto charset detection causes multiple POST DATA warnings when entering form[form sub]
| Assignee | ||
Comment 38•24 years ago
|
||
i'm wondering if i should dup bug 116217 to this one.
Comment 39•24 years ago
|
||
Since I believe 116217 is a dup nominating this one as nsbeta1 and mozilla 1.0
blocker.
A major bug since can cause not able:
1. to log somewhere in (the bank example in bug 116217)
2. you can lost access to places that apply indentification and you enter wrong
access passwords. I couldn't log in anymore with the same bank example when I
entered wrong password and even the right password was not applyed. I was forced
to call to the bank suppport for re-opening my e-account and to use another browser.
3. makes 2 bets on estonian auction site (www.osta.ee) -> you place your offer,
mozilla promts you about the POST DATA, then immediatelly shows that someone
have placed a better offer, but if you return to the bet page thrue history and
reload it there's already listed your name and offer as the best offer.
I sudgest to rase the severity.
Tnx for listening.
Keywords: mozilla1.0,
nsbeta1
Comment 40•24 years ago
|
||
This is essentially a duplicate of bug 61363 -- the charset detector reloads the
page once it detects the charset.
Depends on: latemeta
| Assignee | ||
Comment 41•24 years ago
|
||
marking as a dup
*** This bug has been marked as a duplicate of 116217 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Updated•24 years ago
|
No longer blocks: profile-corrupt
Comment 43•23 years ago
|
||
*** Bug 138897 has been marked as a duplicate of this bug. ***
Updated•7 years ago
|
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•