php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #20288 post-inputs "lag behind"
Submitted: 2002-11-06 12:03 UTC Modified: 2002-11-21 17:12 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: miker at sundialservices dot com Assigned:
Status: No Feedback Package: Unknown/Other Function
PHP Version: 4.3.0-pre2 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
37 + 49 = ?
Subscribe to this entry?

 
 [2002-11-06 12:03 UTC] miker at sundialservices dot com 
Suppose I have two forms with a submit-button on 
each.  The first form takes "submit=Form1" and in 
response, redirects the user to Form2.  On this 
form, "submit=Form2." 
-- 
Trouble is, when I click the button having 
arrived on Form2, I might see an error message 
(from my app) like "Unknown submit=Form1".  In 
other words, Form2 telling me that it's getting a 
value that it doesn't understand:  it is getting 
a submit-value that is lagging-behind or 
out-of-date.  (Value should have been 'Form2'.) 
-- 
I saw this after upgrading PHP.  I see similar 
problems with familiar tools like phpMyAdmin, 
which doesn't update values when editing database 
tables because of this effect. 
-- 
It's bewildering and hard-to-explain, but very 
real and very, very urgent.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-11-07 19:08 UTC] sniper@php.net 
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.
 [2002-11-07 19:50 UTC] miker at sundialservices dot com 
I don't believe or accept this closure.  You 
folks close bugs as "bogus" with a stock-reply 
much too quickly. 
--  
This is found in 4.3.0-dev built from source on 
Oct 24, 2002 with options: 
 
 './configure' '--with-apxs' '--with-mysql' 
'--with-exec-dir' '--with-regex' '--with-gettext' 
'--with-jpeg-dir' '--with-png' '--with-zlib' 
'--enable-magic-quotes' '--enable-debugger' 
'--enable-sockets' '--enable-sysvsem' 
'--enable-sysvshm' '--enable-track-vars' 
'--with-xml' '--with-imap' '--with-kerberos' 
'--with-imap-ssl' 
 
I described the behavior I am seeing very, very 
clearly.  It looks like the forms are reacting to 
"old" POST input.
 [2002-11-07 20:13 UTC] sniper@php.net 
What I was expecting to get is a simple, short example script that I can just cut'n'paste and run on my dev server
to see the problem with my own eyes. If you had bothered reading the information provided in the URL that is included
in that "stock-reply", I wouldn't have to be wasting my time
telling you this.

Please do remember that PHP is an opensource project and we're all volunteers here. It also means that we're not getting PAID for doing this..
 [2002-11-21 17:12 UTC] sniper@php.net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Apr 19 14:01:30 2024 UTC