Bug 19551 - Restricting the sending of the HTTP Referrer
Summary: Restricting the sending of the HTTP Referrer
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All OS X 10.5
: P2 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-15 04:37 PDT by Markus Wulftange
Modified: 2010-04-20 16:08 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Wulftange 2008-06-15 04:37:16 PDT
There should be an option similar to the Cookie Acceptance option wether the HTTP referrer is automatically sent or not.

Another good option would be to just send a HTTP referrer to the same website/host name:

  Source                  Destination           Sending Referrer? (Reason)
  ===============================================================================
  http://example.com/  -> http://example.com/   true  (same host name)
  http://example.com/  -> http://example.net/   false (different host names)
  https://example.com/ -> http://example.com/   false (HTTP to HTTPS)
  https://example.com/ -> https://example.com/  true  (same scheme and host name)
  https://example.com/ -> https://example.net/  false (different host names)
Comment 1 Alexey Proskuryakov 2010-04-20 16:08:50 PDT
WebKit makes it possible for embedding applications to control headers of requests being sent. If you'd like it to be a Safari option, then this is out of scope for WebKit open source bug database. Please file a bug with Apple via <http://bugreport.apple.com>.