referrer not sent for images loaded via javascript new Image()

RESOLVED FIXED in Future

Status

()

Core
Layout: Images
RESOLVED FIXED
16 years ago
15 years ago

People

(Reporter: Chris Casciano, Assigned: Stuart Parmenter)

Tracking

({dataloss})

Trunk
Future
All
Windows NT
dataloss
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
I have a little stat tracking "bug" embedded in the page give above. It's just
used to record the site visitor's viewable browser dimentions. While viewing the
apache log files to extract the info I noticed that Mozilla was the only browser
where the referrer field was *not* valued. This was the case with the following
user agent strings:

Mozilla/5.0 (Macintosh; N; PPC; en-US; m18) Gecko/20010131 Netscape6/6.01

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3) Gecko/20010801

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.3+) Gecko/20010806

[only a few sorry, i just created this tracker]
This information is valued for ever other user agent that has made the image
request [IE4,5 & 6 & NN4.x on both mac and pc]

---

The code that is being exected is as follows:

function triggerbug() {
var iWidth = (window.innerWidth) ? window.innerWidth : document.body.offsetWidth;
var iHeight = (window.innerHeight) ? window.innerHeight :
document.body.offsetHeight;

var bug = new Image();
bug.src = "bug.gif?clientw=" + iWidth + "&clienth=" + iHeight;
}

---

now, the linked site doesn't require referrer to function, it's just something i
noticed cause i was in my logs. That's not to say other sites do not rely on
this functionality to work.
->imglib
Component: Browser-General → ImageLib

Updated

16 years ago
Summary: referrer not being reported to logs when image is called via javascript → referrer not sent for images loaded via javascript new Image()

Comment 2

16 years ago
reassign to default owners.
Assignee: asa → pavlov
QA Contact: doronr → tpreston

Comment 3

16 years ago
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

16 years ago
Blocks: 61660
(Assignee)

Updated

16 years ago
Target Milestone: --- → Future
Is this still an issue?  There was a recent fix to send referer for image in a
much wider set of cases....
(Reporter)

Comment 5

16 years ago
I don't believe it is, usless this fix landed extremely recently (read post
0.9.9). Looking at some recent data written by the script at
http://placenamehere.com/2001-09-11/ I see the following in my logs:

XXX.XXX.XXX.XXX - - [11/Mar/2002:21:58:31 -0500] "GET
/2001-09-11/bug.gif?clientw=978&clienth=1007 HTTP/1.1" 200 43 "-" "Mozilla/5.0
(X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204"

XXX.XXX.XXX.XXX - - [13/Mar/2002:05:33:33 -0500] "GET
/2001-09-11/bug.gif?clientw=1491&clienth=1016 HTTP/1.1" 200 43 "-" "Mozilla/5.0
(Windows; U; Windows NT 5.0; en-US; rv:0.9.9+) Gecko/20020310"

XXX.XXX.XXX.XXX - - [13/Mar/2002:17:06:16 -0500] "GET
/2001-09-11/bug.gif?clientw=1059&clienth=908 HTTP/1.1" 200 43 "-" "Mozilla/5.0
(Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311"

XXX.XXX.XXX.XXX - - [14/Mar/2002:09:24:14 -0500] "GET
/2001-09-11/bug.gif?clientw=842&clienth=654 HTTP/1.1" 200 43 "-" "Mozilla/5.0
(Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204"


In contrast here is what IE is giving me in the same scenario:

XXX.XXX.XXX.XXX - - [18/Mar/2002:14:18:07 -0500] "GET
/2001-09-11/bug.gif?clientw=1024&clienth=603 HTTP/1.0" 200 43
"http://www.placenamehere.com/2001-09-11/" "Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.1; Q312461)"
(Assignee)

Updated

16 years ago
Component: ImageLib → Image: Layout
(Reporter)

Comment 6

15 years ago
just revisiting my bugs in 1.0/recent trunks... for the record I'm still seeing
this bug.

Updated

15 years ago
Keywords: dataloss

Comment 7

15 years ago
i believe that the patch for bug #145579 fixed this problem.

marking fixed.

-- rick
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.