Update SSL info
This commit is contained in:
parent
d47e3a16f1
commit
b267277dc2
6
web.html
6
web.html
|
@ -52,7 +52,10 @@
|
|||
<li><code>UTF-8</code> (though you should only except characters from the above encodings to work)</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>use the least possible amount of HTTPS: PSPs do not support the most recent TLS protocols and many server configurations will not allow older protocols.</li>
|
||||
<li>
|
||||
use the least possible amount of HTTPS: PSPs only support SSLv3 and many server configurations will not allow it.<br />
|
||||
my best guess is that the <a href="http://en.wikipedia.org/wiki/POODLE">POODLE</a> vulnerability killed the PSP's HTTPS support in late 2014 due to everyone disabling SSLv3.
|
||||
</li>
|
||||
<li>use relative links on ~town: this allows HTTPS users to still use HTTPS, and PSP users to still use HTTP.</li>
|
||||
<li>validate your site against XHTML 1.0, or HTML 4.01</li>
|
||||
<li>the maximum supported JavaScript standard seems to be ECMAScript 3</li>
|
||||
|
@ -102,7 +105,6 @@
|
|||
</ul>
|
||||
</li>
|
||||
<li>Play around with the PSP's RSS feed feature using its <a href="https://www.playstation.com/manual/psp/rss/en/spec.html">extensive documentation</a> and create new feeds</li>
|
||||
<li>Find out which SSL and TLS protocols are actually supported by the PSP</li>
|
||||
<li>Create a Webpack template to build modern HTML/CSS/JS to PSP-compatible websites</li>
|
||||
<li>
|
||||
Build an anti-HTTPS proxy:
|
||||
|
|
Loading…
Reference in New Issue