Closed
Bug 293095
Opened 20 years ago
Closed 20 years ago
"go" button for flight search yields message "cannot redirect to server"
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: rswatson, Assigned: mikepinkerton)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Camino 0.8.3 or newer (downloaded from Camino main page)
As long as I use Camino 0.8.2, it works, but in 0.8.3 or newer I get the "cannot
redirect to server" message
Reproducible: Always
Steps to Reproduce:
1.go to http://www.frontierairlines.com/index.asp
2. attempt to book a flight (enter airports and dates)
3. click the green "go" button
Actual Results:
message on blank screen "unable to redirect to server" (or something similar)
Expected Results:
should go to a page listing multiple flight options for the selected days
Only a problem with 0.8.3 or newer.
WFM both Camino 0.8.4 and 20050505 0.8+
Assignee | ||
Comment 2•20 years ago
|
||
i get the error the user reports. does this work in firefox and mozilla 1.7.x?
(In reply to comment #2)
> i get the error the user reports. does this work in firefox and mozilla 1.7.x?
Works fine with the Firefox 5/5 nightly. I'm getting the errors with Camino too.
Assignee | ||
Comment 4•20 years ago
|
||
what about the latest ff 1.0.x, which shares the gecko with camino 0.8.3/4?
(In reply to comment #4)
> what about the latest ff 1.0.x, which shares the gecko with camino 0.8.3/4?
Works fine with ff 1.0.3 as well.
It works fine for me using NB and official release. I wonder if it might be isp
related?
No problems for me with Fx 1.0.3, either. I'm with Jasper; it might be
ISP-related, or perhaps proxy-related?
Assignee | ||
Comment 8•20 years ago
|
||
i tried this from home in 084 and it worked fine. must be IP filtering or
proxies that trip it up.
odd though that if you go back to 082 it works.
I was able to reproduce this only once in my vanilla "testing" account (except
not with the Go button, but with the Continue button on the next screen),
whereas that account could repro bug 296401 dozens of times.
Given the relative similarity of this error and the circumstances (Camino 0.8.3
or newer, and that some people could see it but not others, and others browsers
on the same machine worked) to bug 296401, there's still a chance my suggestion
in bug 296401 comment 9 will work.
Does anything else in the 0.8.3 release notes seem like a likely culprit?
http://www.caminobrowser.org/releases/083.html
Can someone check to see if performing the steps I outline in bug 296401 comment
9 fix this bug (and therefore make this bug a dupe of bug 296401)?
Component: Page Layout → General
Are people still seeing this problem? If so, has anyone tested the work-around
in bug 296401 comment 9?
Any objections to closing this WFM?
If this issue reappears, you can reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•