Closed
Bug 375701
Opened 18 years ago
Closed 9 years ago
301 redirects not showing correct page on a Cold Fusion Redirect
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
INVALID
People
(Reporter: bmcintyre, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/312.8.1 (KHTML, like Gecko) Safari/312.6
Build Identifier: 10.3.9
I am utilizing a 301 redirect for Coldfusion pages from an old site we did. So when the person goes to this page it redirects, but the code for the page is viewed and not the actualy page?
Reproducible: Always
Steps to Reproduce:
1. Type in address above
2.
3.
Actual Results:
It shows the code for the redirect page and not the actualy page that I redirected too.
Expected Results:
Shows the exact redirect page that I stated in the Cold Fusion mod rewrite.
Thanks for your help.
Updated•18 years ago
|
Component: Error Console → Networking
OS: Mac OS X → All
Product: Firefox → Core
QA Contact: javascript.console → networking
Hardware: Macintosh → All
Comment 1•16 years ago
|
||
Problem is on the server side.
http://www.kittyhawk.com/hg is redirected to http://www.kittyhawk.com/hg/ without problem. http://www.kittyhawk.com/hg/ is redirected to http://www.kittyhawk.com/hanggliding/introduction.cfm but the response is wrong. There is Content-Length: 176 in response header but whole message has 177 bytes. See output from:
echo -ne "GET /hg/ HTTP/1.1\r
Host: www.kittyhawk.com\r
\r
" | nc www.kittyhawk.com 80 > output
The last character (space) isn't consumed and will appear as first character in the next response. So the response will be " HTTP/1.1...", this is recognized as HTTP/0.9 response and the whole reply including headers is displayed as text file.
Bug 363109 is similar though not the same. Anyway fixing it according to comment #14 (https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c14) would fix this bug too.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•