Tom
Tom
Fix #11
Also, standard redirect and error redirect could be improved: https://explainshell.com/explain?cmd=ls+%3E+output.log+2%3E+error.log
Also, Let's Encrypt CP is updated in that direction: https://github.com/letsencrypt/cp-cps/compare/b9e9a5678c...bc0499a213#diff-43f79d14d36303bbae3da9268d7a2238R361-R399
lazy loading for `img` has been added in 20.3.16 https://github.com/svenkreiss/html5validator/blob/main/vnujar/CHANGELOG.md#20316 and is planned for `iframe` for the upcomming version.
Additionally, the example only talks about these two syntax: > jQuery.Event( "click" ) and > jQuery.Event( "keydown", { keyCode: 64 } ); But the source says it may be used...
> the bicycle path is drawn on top of the primary road, not masked by it. Yes, where there is a bicycle path, it's correct, the problem is only between...
- With the current solution, if the application send for example 50% fake requests the server **knows** the client has 50% of the applications requested. It know each application has...
> I would prefer not to diverge from that, although we could update if they do Seams sensible > I suppose 1024-bit DH wouldn't be super-dangerous And there isn't much...
Most links are fixed by #739 For "Differences from Current ACME Draft" there is #740 For `getinvolved.md`, maybe it can also talk about https://tools.ietf.org/html/draft-ietf-acme-tls-alpn-01 and https://tools.ietf.org/html/draft-ietf-dnsop-let-localhost-be-localhost-02 ?
A new one would be perfect!