From Bugzilla Helper: User-Agent: Mozilla/4.75 [en] (X11; U; FreeBSD 4.2-BETA i386; Nav) BuildID: 2000101015 mozilla doesent send an Referer: Header when requesting content of an iframe. Reproducible: Always Steps to Reproduce: 1. open the page 2. 3. Actual Results: null.gif is show because our banner engine checks for the referer haeder to verify the site is allowed to use our banner Expected Results: Ad banner shown in iframe
Gerhard Schmidt, I see a banner appearing on your URL. So I guess it's working. I'm using the 2000111704 build on Windows 98.
Thats because we have deaktivated referrer check for user-agent matching *gecko* because some of our customers complained about Netscape 6 not working also. But this is only a Temporary Fix.
This works fine for me. Platform: PC OS: Windows 98 Mozilla Build: #2000121804 M18 Trunk Build Marking WORKSFORME reopen if its still a problem.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
It work because have build a Temporary workaround in our Banner engine but that don´t change the bug. I have already wrote this in an comment on this bug.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Well can you setup a test case we can work on? Otherwise we cant fix the problem.
I've set up a testcase for this at http://www.zbarsky.org/~bzbarsky/moztest/referer.html Indeed, Mozilla does not pass a Referer: header to the frames in a frameset (linux build 2000-12-05-08). NS 4.x does.
Marking NEW and adding keyword testcase.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Marking new for real
Setting milestone to mozilla0.9.1. Eric is this a common issue?
Target Milestone: --- → mozilla0.9.1
Seems it is a pretty common problem.... :) *** This bug has been marked as a duplicate of 57076 ***
Status: NEW → RESOLVED
Last Resolved: 18 years ago → 18 years ago
Resolution: --- → DUPLICATE
QA Contact update
QA Contact: petersen → amar
Status: RESOLVED → VERIFIED
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.