Closed Bug 225682 Opened 21 years ago Closed 16 years ago

Unable to open the URL http://www.net.tv.br

Categories

(SeaMonkey :: General, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cobra, Unassigned)

References

()

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

When I try to open http://www.net.tv.br on firebird 0.7 nothing happens. On
Internet Explorer 6 it opens normally. I tried to change the user agent to IE on
firebird and nothing happened too.

Reproducible: Always

Steps to Reproduce:
1.Type http://www.net.tv.br on address bar
2.Hit enter

Actual Results:  
The tab title changed to (Untitled) and "Done" appeared on status bar

Expected Results:  
Opened the page.
I see the same thing on the Mac version (so Hardware and OS can be set to
"All"). As expected, I also see this in the standard Mozilla browser, so the
Product should probably be shifted to "Browser" as well.

The supplied URL, http://www.net.tv.br , leads to http://nettv.globo.com .
That page only has a tiny bit of code in its body: <meta http-equiv ="Refresh"
content ="0; URL =http://nettv.globo.com/NETBr/">

On Mozilla and FB, it stops at this point.

On Safari, this leads the browser to draw the page
http://nettv.globo.com:0/NETBr/br/home/index.jsp

If I try to enter that jsp URL manually into the location bar in Mozilla or FB,
it won't go anywhere. It stays on the last page viewed. If I remove the ":0" bit
from the address, or set it to 80, it loads. So the browsers don't seem to like
a port address of zero.
Confirming.

OS->All
Platform->All
Product->Browser
Component->Browser-General

I know nothing about meta refreshes but I'm guessing this one's written wrong.
Status: UNCONFIRMED → NEW
Component: General → Browser-General
Ever confirmed: true
OS: Windows XP → All
Product: Firebird → Browser
Hardware: PC → All
Version: unspecified → Trunk
The original page for this bug works now, but that seems to be because they're
no longer using the port 0 string in the URL. I assume this bug still exists,
but I don't know of another page it can be tested on.
Product: Browser → Seamonkey
Assignee: bross2 → general
QA Contact: general
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
No way of resolving this as FIXED unless we want to call it Tech Evangelism

-> WORKSFORME
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.