You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2015/05/21 10:38:13 UTC

No more X- prefix in HTTP headers? (was: Introducing Tracer...)

Hi,

On Thu, May 21, 2015 at 10:30 AM, Robert Munteanu <ro...@apache.org> wrote:
> ...the X- prefix is deprecated with RFC6648 [1]..

Interesting, so IIUC the plan is just to use our own prefix like
Sling- for custom headers, and hope for the best?

-Bertrand

> [1]: http://tools.ietf.org/html/rfc6648

Re: No more X- prefix in HTTP headers? (was: Introducing Tracer...)

Posted by Chetan Mehrotra <ch...@gmail.com>.
Hi Roy,

On Thu, May 21, 2015 at 11:59 PM, Roy Fielding <fi...@adobe.com> wrote:
> If your application sends messages outside its own memory space, X- is not appropriate for
> those fields

Would not that be the case for all headers i.e. as it involves remote
communication.

If using X-Sling-Tracer is not appropriate then what should be used
'Sling-Tracer' or just 'Tracer' as using 'Sling-' as prefix is again
kind of namespacing

Chetan Mehrotra

Re: No more X- prefix in HTTP headers? (was: Introducing Tracer...)

Posted by Roy Fielding <fi...@adobe.com>.
> On May 21, 2015, at 1:40 AM, Chetan Mehrotra <ch...@gmail.com> wrote:
> 
> Repeating my answer on the other thread
> 
> ===
> That recommendation is meant for headers which are
> meant to be used in a wider context. Header which are very much
> specific to application are better prefixed to indicate that they are
> custom ones IMHO [2]. So I would prefer naming them X-Sling-Tracers.
> ===
> 
> Chetan Mehrotra
> [2] http://stackoverflow.com/a/19640336/1035417

Only if they are not sent on the Internet.  The sole purpose of the X- prefix is to prevent
name conflicts between the outside world and whatever might be internal to your own application.
If your application sends messages outside its own memory space, X- is not appropriate for
those fields (because they are now part of the outside world).

....Roy


Re: No more X- prefix in HTTP headers? (was: Introducing Tracer...)

Posted by Chetan Mehrotra <ch...@gmail.com>.
Repeating my answer on the other thread

===
That recommendation is meant for headers which are
meant to be used in a wider context. Header which are very much
specific to application are better prefixed to indicate that they are
custom ones IMHO [2]. So I would prefer naming them X-Sling-Tracers.
===

Chetan Mehrotra
[2] http://stackoverflow.com/a/19640336/1035417



On Thu, May 21, 2015 at 2:08 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi,
>
> On Thu, May 21, 2015 at 10:30 AM, Robert Munteanu <ro...@apache.org> wrote:
>> ...the X- prefix is deprecated with RFC6648 [1]..
>
> Interesting, so IIUC the plan is just to use our own prefix like
> Sling- for custom headers, and hope for the best?
>
> -Bertrand
>
>> [1]: http://tools.ietf.org/html/rfc6648