W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2014

Re: [whatwg] HTTP status code from JavaScript

From: Michael Heuberger <michael.heuberger@binarykitchen.com>
Date: Sun, 25 May 2014 23:48:26 +1200
Message-ID: <5381D88A.9060909@binarykitchen.com>
To: whatwg@lists.whatwg.org
Hi Tobie

>> * It is a redundancy. The browser already knows the status code, just
>> not JavaScript.
> That argument can equally well be used the other way round: it's a
> redundancy to expose in JS something that be easily exposed by the
> server.

I understand your perspective but you cannot compare two entirely
different things. Don't forget that most modern web apps are 99% driven
by JavaScript. If the server returns a 404, JavaScript is still unable
to read the initial HTTP status code. Think about it :)

>> * Adding inline JS <script> slows down the page load.
> In that case, use a meta tag:
>
> <meta name=http-status content=404>
>
> Then in JS:
>
> var status = parseInt(document.querySelector("meta[name=http-status]").getAttribute("content"));
>
> Should this pattern become pervasive, it might bathe sense to
> standardize it and expose it in JS. Frankly, though, it's the first
> time I hear of such a request.

That would work but is an overhead, a redundancy. Why add another meta
tag if the status code is already in the HTTP header??

Yes, it's interesting why nobody has suggested this before. There is
always a first time. Probably I am the first to ask for this feature
because I've been working heavily with SPA's and node.js in the recent
years.

Really, it would be awesome if JavaScript could read the HTTP status code!

Michael

-- 

Binary Kitchen
Michael Heuberger
4c Dunbar Road
Mt Eden
Auckland 1024
(New Zealand)

Mobile (text only) ...  +64 21 261 89 81
Email ................  michael@binarykitchen.com
Website ..............  http://www.binarykitchen.com
Received on Sunday, 25 May 2014 11:49:00 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:28 UTC