All users were logged out of Bugzilla on October 13th, 2018

"Redirection limit for this URL exceeded..." in www.nytimes.com

RESOLVED INVALID

Status

()

RESOLVED INVALID
16 years ago
16 years ago

People

(Reporter: thkaras, Assigned: darin.moz)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Prior to v. 1.3, this error was returned when one tried to open an article from
the New York Times summary pages. With 1.3, articles will now open, but the
"e-mail this article" feature returns this error.

Reproducible: Always

Steps to Reproduce:
1. Load www.nytimes.com
2. Load an article from that page
3. Click "e-mail this article" option.

Actual Results:  
See above

Expected Results:  
Open page for addressing e-mail from New York times sending the article.

I believe this error is computer and OS independent (at least between Windows
2000 and Windows XP).

Comment 1

16 years ago
Try following the steps in bug 170039 to resolve this issue.

Comment 2

16 years ago
->networking
Assignee: asa → darin
Component: Browser-General → Networking: HTTP
QA Contact: asa → httpqa
(Assignee)

Comment 3

16 years ago
reporter: have you placed any restrictions on when sites may set cookies on your
machine?  often preventing a site from setting a cookie will cause this error to
occur.

Updated

16 years ago
Component: Networking: HTTP → Cookies
QA Contact: httpqa → cookieqa
Summary: Message "Redirection limit for this URL exceeded. Unable to load page" received when attempt to use "e-mail this article" feature from a an article page in www.nytimes.com → "Redirection limit for this URL exceeded..." in www.nytimes.com
(Assignee)

Comment 4

16 years ago
reporter sent mail indicating that indeed nytimes.com was listed as a site that
could not set cookies.

marking INVALID.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.