[Tickets #8502] Maintenace tasks don't do anything
bugs at horde.org
bugs at horde.org
Wed Aug 19 09:38:41 UTC 2009
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8502
------------------------------------------------------------------------------
Ticket | 8502
Created By | Jan Schneider <jan at horde.org>
Summary | Maintenace tasks don't do anything
Queue | IMP
Version | Git master
Type | Bug
State | Assigned
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Slusarz
------------------------------------------------------------------------------
Jan Schneider <jan at horde.org> (2009-08-19 05:38) wrote:
After confirming the maintenance tasks, nothing happens, I get a white screen.
Network traces from Firebug:
URL:
http://.../hordegit/services/logintasks.php?app=imp&Horde=7e0adb0399202dd58c62b9958a69dcb5
Request header:
Host: php5.wg.de:8888
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13)
Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language:
de-de,de;q=0.9,en-us;q=0.8,en;q=0.6,en-gb;q=0.5,bs;q=0.4,pl;q=0.3,th;q=0.1
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer:
http://php5.wg.de:8888/hordegit/services/logintasks.php?app=imp&Horde=7e0adb0399202dd58c62b9958a69dcb5
Request POST:
logintasks_confirm_0 on
logintasks_page 1
ok Perform Login Tasks
Response header:
Date: Wed, 19 Aug 2009 09:29:20 GMT
Server: Apache/1.3.29 (Unix) PHP/5.2.9
X-Powered-By: PHP/5.2.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: auth_key=7e0adb0399202dd58c62b9958a69dcb5;
path=/headhorde; domain=php5.wg.de
imp_key=7e0adb0399202dd58c62b9958a69dcb5; path=/headhorde; domain=php5.wg.de
Keep-Alive: timeout=15, max=90
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
The response body is empty. In the network overview Firebug claims it
returned a 302, but I don't see a Location: header in the response.
More information about the bugs
mailing list