I remember once learning that php has a `header` function and have been using 'location:...' since ever (pre-2000) as php was almost always supported by hosters like dreamhost, hostgator, and nearly every Linux install came pre-installed with Apache and the php mod. The meta htttp-equiv was a last resort (like gh-pages). Never really used the JS option unless it was part of the application.
Long polling HTML was popular for a while in the early aughts. Just never close the HTTP connection and stream new HTML elements onto the page. I don’t think that would get along with modern tooling.
Also not widely known: the multipart/x-mixed-replace media type, allowing you to send multiple files and have them replace each other. A simple streaming solution without video, WebSocket, or JavaScript, just an <img>.
Combining it with the referrer tag and you can make some pretty interesting graphs. With frames you can even do Floyd's algorithm.
I made a demo of this about 20 years ago but I think it just confused people. One of my early flops that I thought was cool. It was all in perl and I think there was some JS in there as well but I don't remember anymore. No idea where it is now.
Rewrite it and make a hyped up pitch page. People will call you a genius and I'll pretend not to care
Ahh. This brings back memories. I used to do this when I was using Adobe (Macromedia originally) FLASH back in the day. If no FLASH, show them the shitty version. HAHA. Good times.
You'd be surprised how often Flash was "the shitty version" as it was almost always bloated with long load times, inaccessible content and a lot of pointless stuff that was clearly to impress the client who comissioned it, not the poor user who wanted to find something out.
This is what you get if you learn everything by just googling exactly what you need for the moment. Reading proper books and RFCs are underrated these days.
Maybe because we collectively pretty badly handled knowledge transmission between generations.
For the pioneers the most difficult part of learning CS was to get hardware needed. This mostly determined the technological stack they would then learn.
Nowadays hardware is commodity and the main problem is to determine what the hell you should start learning first because you can't learn everything it has now became humanely impossible.
I was born somewhen in the middle. Because of my first field I wish I could have mastered python. But at that time the python2/3 war was at the highest and you couldn't find reliable documentation. Hell even python3 tutorial kept on blabbering about how python2 concept translated. What was i supposed to do? learn both?
That is why I focused on SQL because at least documentation was quite stable (special thanks to PostgreSQL documentation teams).
I can only imaging the nightmare that must endure rookies frontend dev nowadays.
The noscript tag is the correct way to do this. Server side, when you first generate page content you have no idea if the client has scripting enabled, which is why you include a noscript element to advise the user what to do, or redirect them using a meta tag inside the noscript element.
So all these suggestions below to use server side generated HTTP headers and 302 (or 301) redirects are incorrect...because you won't know, on the first page hit, if the client has scripting enabled. At this point in time only the client knows if scripting is available. Also browser capability sniffing based on headers sent from the client in the first request is not reliable.
I've recently deployed this trick on my company's confluence instance (with an HTML macro) to create a "poor man's" link shortener that allows me to change the link target after the fact.
Also recently deployed it as a very simple server side denounce: when the client first accesses page X a long running operation is dispatched. Subsequent requests for the same resource before it's done processing return a plain HTML response that says "Still thinking about it" and meta refresh after 1 second.
Hehe, the good old html meta redirect. As a kid in the early days of the web I loved to post redirects to porn websites in guestbooks to check if the website was sanitizing the user content properly. Worked way to often :D
This reminds me that while I’ve been programming for a paycheck since 1998 my knowledge growth in html stopped at about 2001. Are there any good courses or recommendations for seasoned pros who never stopped to learn HTML5?
> The term HTML5 is essentially a buzzword that refers to a set of modern web technologies. This includes the HTML Living Standard, along with JavaScript APIs to enhance storage, multimedia, and hardware access.
> You may sometimes hear about "new HTML5 elements", or find HTML5 described as a new version of HTML. HTML5 was the successor to previous HTML versions and introduced new elements and capabilities to the language on top of the previous version, HTML 4.01, as well as improving or removing some existing functionality. However, as a Living Standard HTML now has no version.
Even though it may cover a lot of basic and familiar topics, I think the following is the best (re)introduction to HTML:
Web development has trained me to Google (now often ChatGPT) everything even if I already know how to do it because it changes so much haha
It makes me look stupid in code interviews because I commit very little to memory but professionally it's helped me catch a lot of syntactical upgrades.
Putting 0 value used to be a bad idea, as it was a signal to the browser and various ad blockers and anti viruses that it was a rogue redirect. Wonder if it’s different these days?
gbraad|2 years ago
handsclean|2 years ago
connordoner|2 years ago
donatj|2 years ago
remram|2 years ago
thiht|2 years ago
SoftTalker|2 years ago
moltar|2 years ago
aendruk|2 years ago
https://bugs.chromium.org/p/chromium/issues/detail?id=63107
Reptur|2 years ago
dixie_land|2 years ago
moritzwarhier|2 years ago
It's kind of amazing how parts of the spec that seem dated or obsolete can still be useful today and are even widely used in corner cases.
RobotToaster|2 years ago
lloydatkinson|2 years ago
kristopolous|2 years ago
I made a demo of this about 20 years ago but I think it just confused people. One of my early flops that I thought was cool. It was all in perl and I think there was some JS in there as well but I don't remember anymore. No idea where it is now.
Rewrite it and make a hyped up pitch page. People will call you a genius and I'll pretend not to care
pooper|2 years ago
<script>{setInterval(function(){document.location.reload();},5000)}</script>
now
for example, I tried out view-source:https://archive.fo/wip/RpDSg
does anyone else remember seeing meta refresh? if so, any idea why they switched to javascript reload
stuckkeys|2 years ago
MrVandemar|2 years ago
GrumpyNl|2 years ago
Puts|2 years ago
Twisell|2 years ago
For the pioneers the most difficult part of learning CS was to get hardware needed. This mostly determined the technological stack they would then learn.
Nowadays hardware is commodity and the main problem is to determine what the hell you should start learning first because you can't learn everything it has now became humanely impossible.
I was born somewhen in the middle. Because of my first field I wish I could have mastered python. But at that time the python2/3 war was at the highest and you couldn't find reliable documentation. Hell even python3 tutorial kept on blabbering about how python2 concept translated. What was i supposed to do? learn both?
That is why I focused on SQL because at least documentation was quite stable (special thanks to PostgreSQL documentation teams).
I can only imaging the nightmare that must endure rookies frontend dev nowadays.
dmd|2 years ago
ssttoo|2 years ago
https://developer.mozilla.org/en-US/docs/Web/HTTP/Redirectio...
teh_klev|2 years ago
So all these suggestions below to use server side generated HTTP headers and 302 (or 301) redirects are incorrect...because you won't know, on the first page hit, if the client has scripting enabled. At this point in time only the client knows if scripting is available. Also browser capability sniffing based on headers sent from the client in the first request is not reliable.
For more info see:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/no...
jdlshore|2 years ago
scarface74|2 years ago
riffic|2 years ago
masenf|2 years ago
Also recently deployed it as a very simple server side denounce: when the client first accesses page X a long running operation is dispatched. Subsequent requests for the same resource before it's done processing return a plain HTML response that says "Still thinking about it" and meta refresh after 1 second.
unknown|2 years ago
[deleted]
crooked-v|2 years ago
9034725985|2 years ago
<meta http-equiv="refresh" content="300"> to do speed test from fast.com
see:
view-source:https://angularten.github.io/
latchkey|2 years ago
unknown|2 years ago
[deleted]
TRiG_Ireland|2 years ago
rawbert|2 years ago
mikece|2 years ago
lioeters|2 years ago
> You may sometimes hear about "new HTML5 elements", or find HTML5 described as a new version of HTML. HTML5 was the successor to previous HTML versions and introduced new elements and capabilities to the language on top of the previous version, HTML 4.01, as well as improving or removing some existing functionality. However, as a Living Standard HTML now has no version.
Even though it may cover a lot of basic and familiar topics, I think the following is the best (re)introduction to HTML:
HTML: HyperText Markup Language - https://developer.mozilla.org/en-US/docs/Web/HTML
onetrickwolf|2 years ago
It makes me look stupid in code interviews because I commit very little to memory but professionally it's helped me catch a lot of syntactical upgrades.
javajosh|2 years ago
moltar|2 years ago
bryanrasmussen|2 years ago
fergie|2 years ago
notRobot|2 years ago
[deleted]
vermilingua|2 years ago
vimax|2 years ago
arbuge|2 years ago
Uptrenda|2 years ago