Even in the single domain case, there could be lots of apps and resources, and the Referer header could be used for whatever use cases that this header is used for non-XHR requests today. One use case is to find out the context in which the request was generated for analytics purposes. It would be useful to encourage browsers to send this header.

Subbu

On 6/28/06, Mark Baker <[EMAIL PROTECTED]> wrote:

Sven,

I think the value's pretty low for the single domain case, no?  Since
requests will only ever be made back to the server that served the
script, that would make for a pretty information-free referer log
AFAICT.

Do you have some specific use cases?

Mark.

On 6/23/06, Sven Neuhaus <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> currently, there is no standard behaviour for XMLHttpRequests regarding the
> Referer HTTP header - some browsers send it, others don't [see also
> https://bugzilla.mozilla.org/show_bug.cgi?id=170477].
>
> As a web developer, I would welcome it if the referer header was sent by as
> many browsers as possible when using XMLHttpRequests. It helps a lot when
> analyzing problems and figuring out the origin of requests.
> Please include the Referer header in the specification as a recommended
> header for HTTP requests generated by the XMLHttpRequest object.
>
> Suggestion:
> 'HTTP requests SHOULD by default include the "Referer" HTTP header.'
>
> This probably belongs in the description of the "send" method.
>
> Regards,
> -Sven Neuhaus
>
>
>




--
------------------------------
http://www.subbu.org

Reply via email to