# ? Aug 22, 2016 01:09 |
|
|
# ? May 2, 2024 22:02 |
---------------- |
|
# ? Aug 22, 2016 01:12 |
---------------- |
|
# ? Aug 22, 2016 01:13 |
---------------- |
|
# ? Aug 22, 2016 01:14 |
---------------- |
|
# ? Aug 22, 2016 01:15 |
---------------- |
|
# ? Aug 22, 2016 01:20 |
---------------- |
|
# ? Aug 22, 2016 01:21 |
---------------- |
|
# ? Aug 22, 2016 01:25 |
---------------- |
|
# ? Aug 22, 2016 01:29 |
|
|
# ? Aug 22, 2016 01:32 |
What the...
---------------- |
|
# ? Aug 22, 2016 01:34 |
|
misty mountaintop posted:What the... I see them. I'll have to see if any of my tapes survived https://i.imgur.com/QKTkerO.mp4 |
# ? Aug 22, 2016 01:43 |
|
they're showing up fine on my Awful app, so it's probably just Chrome
|
# ? Aug 22, 2016 01:43 |
|
HighwireAct posted:they're showing up fine on my Awful app, so it's probably just Chrome I use chrome and they work fine for me
|
# ? Aug 22, 2016 01:44 |
|
my only record:
|
# ? Aug 22, 2016 01:45 |
|
thepiratebae.se posted:I use chrome and they work fine for me what the…
|
# ? Aug 22, 2016 01:45 |
|
I had an actual physical beat-tape but I mailed it to R-Type's Nephew when I sent him the 3DS |
# ? Aug 22, 2016 02:44 |
|
HighwireAct posted:they're showing up fine on my Awful app, so it's probably just Chrome You're accessing the site through https://forums.somethingawful.com/ in Chrome, Chrome keeps updating its SSL policies and the internet hasn't really caught up but it's because Chrome is viewing the forums through an SSL and the host server isn't hosting them through an SSL. Just change your forums url to http:// or drop that part off altogether |
# ? Aug 22, 2016 02:46 |
|
Shakill OReal posted:You're accessing the site through https://forums.somethingawful.com/ in Chrome, Chrome keeps updating its SSL policies and the internet hasn't really caught up but it's because Chrome is viewing the forums through an SSL and the host server isn't hosting them through an SSL. Just change your forums url to [url]http://[/url] or drop that part off altogether o welp thanks for the tip
|
# ? Aug 22, 2016 03:05 |
|
|
# ? May 2, 2024 22:02 |
|
it's a security feature all modern browsers do it. all http resources are blocked in a https page because if someone was to do a man in the middle attack on a javascript file for example the could pretty easily copy or edit the content of the page defeating the point of the encryption. occasionally there are vulnerabilities possible in the handling other file types so as a blanket rule it's disallowed. SA could work around this by automatically changing the url to https for a list of known sources though or just // instead of [url]http://[/url] or [url]https://[/url] which just means use the parent protocol. |
# ? Aug 22, 2016 10:50 |