| API | Firefox | Safari | Chromium | IE |
|---|---|---|---|---|
| Подписка на beforeunload | ✘ | ✔ | ✔ | ✘ |
| Подписка на unload | ✘ | ✔ | ✔ | |
| Незавершённые запросы XHR/fetch | ✘ | ✔ | ✘ в планах прерывать запрос и вызывать onerror при восстановлении страницы | |
| Незавершённые запросы за ресурсами | ✘ кроме favicon |
a gist to recap the current status, also available as library picker!
do one thing only and do it well
This gist summarizes the handleEvent(event) pattern features, something standard, something described by me many times, written in my tiny book, tweeted about, and yet it's something most Web developers ignore.
┌---------------------------------┐
var handler = { | any object that inherits or |
| ######################################################################################################## | |
| # This config enables us to: | |
| # - Resize | |
| # - Rotate | |
| # ...the resident images on an upstream server, with Nginx Server in our hand, On the fly! | |
| # - Just by using arbitrary Query Parameters | |
| # ...and | |
| # - Cache the transformed image by address. | |
| # | |
| # Well, I got the Idea from https://stumbles.id.au/nginx-dynamic-image-resizing-with-caching.html |
This is an alternative to the Modern Script Loading tchnique, that doesn't need to wait for the load event.
This technique has been successfully tested down to IE9.
<!DOCTYPE html>
<html lang="en">
This is some sort of answer to recent posts regarding Web Components, where more than a few misconceptions were delivered as fact.
Let's start by defining what we are talking about.
As you can read in the dedicated GitHub page, Web Components is a group of features, where each feature works already by itself, and it doesn't need other features of the group to be already usable, or useful.
| package main | |
| import ( | |
| "encoding/json" | |
| "fmt" | |
| "io/ioutil" | |
| "log" | |
| "net/http" | |
| "os" | |
| "time" |
This configuration enables NGINX to validate an authentication token against an authorization server by using OAuth 2.0 Token Introspection (RFC 7662). This solution uses the auth_request module and the NGINX JavaScript module to require authentication and perform the token introspection request.
By default, the client's authentication token is expected as a bearer token supplied in the Authorization header. If supplied elsewhere in the HTTP request, the $access_token variable must be configured to specify where to obtain the token.
Token introspection requests are authenticated. By default, the $oauth_client_id and $oauth_client_secret variables are used to perform HTTP Basic authentication with the Authorization Server. If only the $oauth_client_secret variable is specified then that value is used
