Problem when connecting via provider which lead user to its home site

RESOLVED INVALID

Status

SeaMonkey
General
RESOLVED INVALID
15 years ago
13 years ago

People

(Reporter: leschij, Assigned: asa)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130

If I have a (arbitrary) page opened (e.g. out of cache), dial in to the internet
using a provider which uses to lead user to its home site (e.g.
http://www.freenet.de/customerindex.html) at first and then try to open a link
on the opened page, home site of the provider is opened (in I-Explorer I get
sonnected to the site I really want to see). 

Even worse - if I change provider to one without home site linking, and try to
open the link again, I still get connected to the former provider's home page,
even if I can see the right URL in the status bar on the bottom of the browser's
window.

P.S.: I use to block the provider's homepage using Outpost Firewall (free
edition). So I get Outpost-message "The web page being accessed was blocked bla
bla..." instead of provider's site. Problem is, that I continue to get this
message even after I have shut down Outpost.

Reproducible: Always

Steps to Reproduce:
1. Open an arbitrary page 
2. Open internet connection via provider like Freenet (links user to its home    
   site)
3. Click on a link at the opened page - you will be taken to provider's page.
4. Abort loading.
5. Change provider.
6. Click on the same link - you will be taken to former provider's page again.
Actual Results:  
See above

Expected Results:  
The best solution is to suppress provider's site at all.

At least this page shouldn't be memorized by browser so that it is opened again
instead of the desired link even if you don't use this provider any more.

I have had the same problemwhen I loaded "Language and content Packs" using the
same provider.

Comment 1

15 years ago
Reporter: Can you reproduce this bug with a recent build of Mozilla (for
example, 1.4rc3)? 

If so, then please comment again with details. 
If not, then please resolve this bug as WORKSFORME. Thanks.
(Assignee)

Comment 2

14 years ago
without further response from the reporter, resolving as invalid.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.