![]() ![]() Wireshark comes to the rescue though, that amazing packet capture tool that has got me out of many a jam. You might want to start looking at what is going over the wire, to debug things (like, why doesn't push seem to be working for me), which is now frightfully complicated, given that the stream is binary, and most likely to be encrypted. If you check your browser's developer console you should see quietly somewhere that there is something mentioning it was http2 and not 1.1 in the response. You can enable HTTP2 on Apache quite easily by ensuring the relevant mod has been loaded:Īnd then updating your virtual host config file to support the protocol:Īnd don't forget to restart apache. You can get one of these for free from LetsEncrypt (there are plenty of blogs and guides out there to deal with using these as they expire every 90 days). On the subject of encryption, HTTP2 is largely only supported over TLS (as it's predecessor SPDY was restricted to this), which means if you want to serve it up, you need to use a x509 certificate ("SSL" certificate). But the world has moved on and wants to do more funky things with HTTP, and given the push recently to get everything encrypted, plain-text means little as TLS/SSL are binary anyway - you're not going to be typing encryption out by hand! ![]() What does this mean? A plain-text protocol is very easy for us humans to interact with, you can easily open a telnet session to a server and type in your GET request and read the response in plain old ASCII. Chiefly, it is a binary protocol instead of a plain-text one. It is fundamentally different from HTTP1.1 which is used by most today. HTTP2 is a new protocol for serving web-pages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |