[horde] Blank page on Horde / IMP

Wed Feb 2 10:29:07 PST 2005

Mike,

Agree that it will be very hard to troubleshoot due to the limited number of 
occurencies...
Unfortunately, my speciality is not PHP/Programming/Web/Application 
development.. I'm just an MCSE and Unix is my hobby and debugging of PHP 
code is not the thing I can perform well.
Certainly, if the concrete instructions will be provided, I'll be happy to 
assist.
>From my side I'll be happy to provide remote access both to my server and to 
my home XP system (PCAnywhere or MS RDS for XP and SSH for server) to 
someone form development team if this can help. Preferable on weekend.

Summarizing all previous posts the sympthoms are:

-----------------
Server side configuration:
RH Fedora Core 3 will all updates installed.
PHP 4.3.10
MySQL 3.23.58
httpd 2.0.52
Horde 3.0.2
Imp 4.0.1
Cyrus-Imapd 2.2.10
--------------------
Client side:
Windows XP Pro SP2 with all current updates
IE 6.0.2900.2180.xpsp_sp2_rtm.040803-2158
Opera 7.54
Firefox 1.0
--------------------
IMAP authentication is used.
It doesn't matter if Horde or IMP performs authentication, result is blank 
page.
Test.php in Horde/IMP are fine. IMAP tests are fine.
IMP/Horde working fine on 10 tested machines from IE.
IMP/Horde is not working (blank page after auth) from my home IE. Other 
users on the mailing list reported that some XP SP1 machines are also 
affected, so seems to be not SP2 changes related issue.
IMP/Horde working fine from my home pc if I use Opera or Firefox.

So, most probably, issue is realted with some "specific" issue with IE 
configuration and not with server side configuration beacuse everything is 
fine form the other machine running XP SP2 IE6 standing nearby.

As for the logs:

horde.log:
Feb 02 21:19:24 HORDE [notice] [imp] Login success for dusha [217.10.40.81] 
to {localhost:993} [on line 150 of "/var/www/html/horde/imp/redirect.php"]

maillog:
Feb  2 21:19:22 dusha imaps[31116]: executed
Feb  2 21:19:23 dusha imaps[30704]: mystore: starting txn 2147487464
Feb  2 21:19:23 dusha imaps[30704]: mystore: committing txn 2147487464
Feb  2 21:19:23 dusha imaps[30704]: starttls: TLSv1 with cipher AES256-SHA 
(256/256 bits new) no authentication
Feb  2 21:19:23 dusha imaps[30704]: login: localhost.localdomain [127.0.0.1] 
dusha plaintext+TLS User logged in

httpd.log
217.10.40.81 - - [02/Feb/2005:21:19:06 +0300] "GET / HTTP/1.0" 301 310
217.10.40.81 - - [02/Feb/2005:21:19:06 +0300] "GET / HTTP/1.1" 200 1850
217.10.40.81 - - [02/Feb/2005:21:19:09 +0300] "GET 
/horde/js/enter_key_trap.js?Horde=52987f8e7e9ab906d4a110351baebcfa HTTP/1.1" 
200 659
217.10.40.81 - - [02/Feb/2005:21:19:09 +0300] "GET /horde/themes/screen.css 
HTTP/1.1" 304 -
217.10.40.81 - - [02/Feb/2005:21:19:09 +0300] "GET 
/horde/themes/mozilla/screen.css HTTP/1.1" 304 -
217.10.40.81 - - [02/Feb/2005:21:19:09 +0300] "GET 
/horde/imp/themes/screen.css HTTP/1.1" 304 -
217.10.40.81 - - [02/Feb/2005:21:19:10 +0300] "GET 
/horde/themes/mozilla/graphics/menu.png HTTP/1.1" 304 -
217.10.40.81 - - [02/Feb/2005:21:19:19 +0300] "POST /horde/imp/redirect.php 
HTTP/1.1" 200 26

httpd.log.error
no entries for this events

blank page source:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; 
charset=windows-1251"></HEAD>
<BODY></BODY></HTML>

And finally, I should mention that if I'll change the URL (after 
authentication and blank page) manually to (for example):
http://server/horde/imp (was http://server/horde/imp/redirect.php) I'm 
getting into IMP mailbox.

Sergey.

----- Original Message ----- 
From: "Michael M Slusarz" <slusarz at bigworm.curecanti.org>
To: <horde at lists.horde.org>
Sent: Wednesday, February 02, 2005 7:39 PM
Subject: Re: Re: [horde] Blank page on Horde

> Quoting Sergey Dushenkov <dusha at mcl.ru>:
>
>> One more guy with an "empty page" problem.... :)
>> Looks like after a few months there will be enough compliants to 
>> investigate
>> the issue further by developers.
>> :)
>
> Except for the fact that, so far, *none* of the devlopers can reproduce 
> this.  So it is very difficult to debug/fix the problem unless the people 
> that are seeing the problem can do a bit of debugging work and tell us 
> eactly where the code is misbehaving.  We are not asking people to fix the 
> code or supply patches; simply letting us know the cause of the problem 
> should be sufficient.
>
> michael
>
> _______________________________________
> Michael Slusarz [slusarz at curecanti.org]
> -- 
> Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org 