| Summary | $_POST is returned empty (causes login loop) |
| Queue | Horde Groupware Webmail Edition |
| Queue Version | 1.2.2 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | chuck (at) horde (dot) org |
| Requester | jason (at) solo-c (dot) demon (dot) co (dot) uk |
| Created | 02/06/2009 (5992 days ago) |
| Due | 02/06/2009 (5992 days ago) |
| Updated | 03/02/2009 (5968 days ago) |
| Assigned | 02/14/2009 (5984 days ago) |
| Resolved | 03/02/2009 (5968 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Feedback
http://cvs.horde.org/diff.php/framework/Browser/Attic/Browser.php?rt=horde&r1=1.153.2.66&r2=1.153.2.67&ty=u
Horde has no influence on that.
PHP applications running on the same server, under the same test
conditions (including the whole simpletest suite); only those forms
built using the horde framework (including a test script I created for
this specific issue) caused the $_PHP to be returned empty.
However, could the suggested workaround be posted as an advisory note
in the Install FAQ to assist other users.
State ⇒ Not A Bug
Horde has no influence on that.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ $_POST is returned empty (causes login loop)
Due ⇒ 02/06/2009
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
shorthand convention for upload_max_filesize and post_max_size in
PHP.INI (e.g. 10G for 10 gigabytes).
Symptoms: Login form stuck in loop, imp/test.php IMAP/POP login form
loops on form submission, or if using auto login form based
administration activities fail (e.g. submitting config setup forms
reports "Invalid application." error).
Diagnosis: $_POST structure is empty on submit, when forms are
configured via Horde Framework methods. $_POST works in other PHP
applications, and test scripts, on the same server not using the
Horde Framework.
Workaround: define values in php.ini in bytes rather than using
(G)igabyte shorthand. Note - have not tested other shorthand
conventions (M or K), potentially these may work as well to set
gigabyte POST transfer sizes.
Test conditions: configure php.ini with "upload_max_filesize = 8G" and
"post_max_size = 10G".
Environment details:
Applicaiton: Horde Groupware Webmail Edition v.1.2.2
OS: Gentoo Linux, 2.6.24-gentoo-r7
PHP: v5.2.8 [error also occurs with earlier 5.2 bases as well]
WWW Server: Lighttpd v1.5.0 (ssl) [error also occurs with v1.4.20)