| Summary | url limit in IE using meta refresh? |
| Queue | IMP |
| Queue Version | 4.0.2 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | eli (at) experthost (dot) com |
| Created | 03/28/2005 (7424 days ago) |
| Due | |
| Updated | 03/28/2005 (7424 days ago) |
| Assigned | |
| Resolved | 03/28/2005 (7424 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
The refresh is necessary to avoid security warnings with IE if using
the "SSL for login" feature. Using overlong URLs is always a bad idea.
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ url limit in IE using meta refresh?
Queue ⇒ IMP
message from the pre/post auth hooks in Horde.
I had not tested its effects in IE until today when a client reported
IMP hanging on redirect.php when trying to log in.
I have since apparently discovered that IE (6, latest w/patches in
WinXP) is apparently exhibiting a 165 character limit when using a
Refresh: header
In redirect.php, I modified line 170 from:
header('Refresh: 0; URL=' . $url);
to:
header('Location: ' . $url);
and it seems to have fixed my problem. The problem was that if if the
URL was longer than 165 characters, IE would not honor the Refresh:
header and just hang. Once using the Location: header, IE redirects
properly and functions fine.
Is there a specific reason to using the Refresh: header in
redirect.php? Can it safely be switched to using Location: instead?
Also, do you notice this same problem with your IE browser (I have
confirmed this on a few IE installs - no problem in Firefox).
Eli.