This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22385 - HTTP basic fetch, referrer is null?
Summary: HTTP basic fetch, referrer is null?
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-16 21:27 UTC by Marcos Caceres
Modified: 2013-06-20 05:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Marcos Caceres 2013-06-16 21:27:02 UTC 
In the basic fetch section for http/https, the spec says: "If request's referrer is not null ..." 

Should that be `null` or do you mean as in missing? I found that bit a little bit confusing.
Comment 1 Anne 2013-06-19 07:45:59 UTC 
As in not having a value. We typically use null for that.
Comment 2 Marcos Caceres 2013-06-19 11:40:14 UTC 
Yeah, it can get a bit confusing because some things actually use the byte string `null` (like Origin). If you think it's ok, then please close.
Comment 3 Anne 2013-06-20 05:39:41 UTC 
When we think of something better, we'll improve it. We might actually end up requiring referrer to be supplied always in due course I think.