RESOLVED FIXED 16993
REGRESSION: Loading page leads to many unexpected redirections
https://bugs.webkit.org/show_bug.cgi?id=16993
Summary REGRESSION: Loading page leads to many unexpected redirections
Robert Royar
Reported 2008-01-24 04:48:35 PST
My university uses Datatel's Webadvisor for all student, staff, and faculty secure interactions. With the original 523.x WebKit as shipped by Apple, the url https://webadvisor.moreheadstate.edu:443 loads normally. With recent nightly builds (at least since January 21, 2008), navigating to the page begins a page load and then goes into a loop--looks as though there are redirections. The server eventually causes Safari to show an error dialog box which states that the cookies have been exhausted for the session and that the browser must be closed and a new login attempted. Note, it looks as though the server believes cookies have already been set. But clearing all cookies for the site does not fix the error. Neither does exiting the nightly build enabled Safari and restarting it. Starting a new Safari with the Apple-shipped webkit does fix the problem. The problem does not occur in Gecko-based browsers. Note that the site access is restricted without a password and account; however, the problem shows up on the initial guest screen. So anyone should be able to verify this.
Attachments
Mark Rowe (bdash)
Comment 1 2008-01-24 05:22:23 PST
Confirmed with TOT. In Safari 3 I am redirected to a URL of <https://webadvisor.moreheadstate.edu:443/webadvisor/webadvisor?&TYPE=M&PID=CORE-WBMAIN&TOKENIDX=4509844897> which then loads correctly. In TOT I am redirected to a similar URL (different TOKENIDX number), which then redirects to a similar URL with TOKENIDX of NULL, which redirects back to a TOKENIDX with a number. It ping-pongs between NULL and a number repeatedly.
Mark Rowe (bdash)
Comment 2 2008-01-24 05:32:54 PST
Alexey Proskuryakov
Comment 3 2008-01-24 11:42:10 PST
Fixed in r29774. Rolled out r29590, which was not a correct fix for <rdar://problem/5692566>.
Note You need to log in before you can comment on or make changes to this bug.