W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

Re: Http header including if ECMA (Javascript) is on and the version

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 17 Oct 2016 14:05:59 +1100
Cc: ietf-http-wg@w3.org
Message-Id: <DE958BCD-8F07-4E30-9A57-F1D14DDB3439@mnot.net>
To: Scott Morgan <scott@adligo.com>
Hi Scott,

My sense is that there isn't substantial interest in taking this into this draft, especially at this late stage (it's almost out of Working Group Last Call). 

What we really need to see is some amount of enthusiasm for adding the header by implementers; due to its nature, the most obvious people to be talking to will be browser vendors.

You might have better luck getting the attention of the appropriate people here:
  https://discourse.wicg.io
(this is effectively a discussion forum for new browser features)

That's not to say that this WG wouldn't standardise it if there was demonstrated implementer interest, of course.

Cheers,


> On 16 Oct. 2016, at 4:26 am, Scott Morgan <scott@adligo.com> wrote:
> 
> Hi All,
> 
>   I have encountered a issue with web design that appears to be part of the http specification.
> I believe that the version of ECMA (Javascript) and if it is on or off should be included with the http request header when sent to a server.  It might fit well into this RFC;
> 
>   https://www.ietf.org/id/draft-ietf-httpbis-client-hints-02.txt
> 
>   Perhaps a new section between 7 & 8 as follows;
> 
> 8.  The ECMA script (Javascript) Client Hint
> 
>    The "ECMA" request header field is a number or text that 
>    indicates the client's current ECMA implementation version.  A blank ECMA
>    hint would indicate that ECMA script is currently turned off.
>      
>      ECMA = Text [32 ASCII characters]
> 
>    If ECMA occurs in a message more than once, the last value
>    should be used to override other occurrences.
>    Examples;
>  
>      #1 ECMA script is turned off
>      ECMA:
> 
>      #2 ECMA script is on the Next version
>      ECMA: Next
> 
>      #3 ECMA script is on version 5.1
>      ECMA: 5.1
> 
> 
>   The basic thing that I am trying to do is determine if Javascript can be used to assemble a html page or if it should be done server side if Javascript is turned off.  Currently I can do this by assuming javascript is on and then redirecting from the browser when it is off using something like;
>  <noscript><meta http-equiv="refresh" content="0; url=/tt/session.html"></noscript>
> 
> When javascript is on I can assemble (and cache most of the repeated parts of the page).
>  i.e. profile these pages in Chrome and check the speed and cacheing;
> http://mokshayoga.com/tt/tuition.html
> then
> http://mokshayoga.com/tt/index.html
> 
> Vs.
> https://www.mokshayoga.com/chicago-yoga-policies.html
> then
> https://www.mokshayoga.com/chicago-yoga-events.html
> 
> Cheers,
> -- 
> Scott Morgan
> President & CEO
> Adligo Inc
> http://www.adligo.com
> 1-866-968-1893 Ex 101
> scott@adligo.com
> By Appointment Only: skype:adligo1?call
> https://www.linkedin.com/in/scott-morgan-21739415
> 
> 
> 
> 
> 
> -- 
> Scott Morgan
> President & CEO
> Adligo Inc
> http://www.adligo.com
> 1-866-968-1893 Ex 101
> scott@adligo.com
> By Appointment Only: skype:adligo1?call
> https://www.linkedin.com/in/scott-morgan-21739415
> 
> 

--
Mark Nottingham   https://www.mnot.net/
Received on Monday, 17 October 2016 03:06:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 17 October 2016 03:06:34 UTC