Comments on: addSizes.js: automatic link file-size generation

By: JasonStockman

JasonStockman — Fri, 31 Oct 2008 07:33:38 +0000

Great concept, I’ll definitely use this when I can.

By: Tribulus

Tribulus — Wed, 01 Oct 2008 12:05:37 +0000

very helpful
thank you

By: natbat

natbat — Tue, 02 Sep 2008 18:33:39 +0000

It may well make a good browser extension, especially with the addition of the untrusted file type check. @westonruter – that is an interesting idea, I might well update the script to do a check with XHR for files on the same domain and resort to json-head otherwise.

btw Dion, ny name is Natalie Downe not ‘Nathalie Downe’.

By: westonruter

westonruter — Tue, 02 Sep 2008 16:03:05 +0000

Seems like this could be easily done without json-head app if the resources are on the same domain. One could simply make a HEAD request with XHR to the resource and then read the Content-Length.

By: btopro

btopro — Tue, 02 Sep 2008 15:52:54 +0000

Building off eyelidlessness’s comment – What if this was an injection / javascript based plugin for a browser? It could scan the page and append the file time / file size as well as flag files as potentially harmful if they aren’t of the types you define.

By: eyelidlessness

eyelidlessness — Tue, 02 Sep 2008 15:25:53 +0000

Another great use for this would be to check the mime-type for untrusted files. It wouldn’t be fool-proof but it could help you to know what you might get with somefileservingscript.php?filename.ext or worse somefileservingscript.php?id.

By: jwlrs

jwlrs — Tue, 02 Sep 2008 13:22:19 +0000

oops, missed the json head bit, duh…

By: jwlrs

jwlrs — Tue, 02 Sep 2008 13:21:04 +0000

Clever. But isn’t the point of such a file size notation to warn you that the file is pretty big before you bother downloading, in effect giving you a choice? In this case, you are downloading it whether you like it or not…. Seems to miss the point, maybe it’s just me