search

prawnsalad / KiwiIRC

This is **DEPRECATED**! Please go to https://github.com/kiwiirc/kiwiirc
https://kiwiirc.com
GNU Affero General Public License v3.0
891 stars 277 forks source link

Safari fails to load assets when using SSL Kiwi Server #903

Closed utoxin closed 7 years ago

utoxin commented 7 years ago

First, I am running the latest dev version now, but initially I was running a version a year or so old. The bug didn't change in behavior at all when I updated.

I recently got a cert for my site, so I configured Kiwi to use it. It works great in every browser except Safari. In Safari, it just sites on a white screen, and if I look at the error console and the network requests, what appears to be happening is that every request to Kiwi is returning the index.html file, regardless of what is actually being requested.

I've used the dev tools to 'Copy as curl', and when I run the curl commands they claim are equivalent, everything works just fine.

I've set up a non-SSL server on the same daemon, and it works fine in Safari.

The SSL server works fine in every browser except Safari.

I'm stumped. Any suggestions for solutions, or requests for additional information are welcome.

prawnsalad commented 7 years ago

If it's loading the index.html for the assets then that suggests the URLs are not being sent to the kiwi server correctly. But only on Safari? That doens't make much sense.

Is your kiwi server public somewhere so we can take a look?

utoxin commented 7 years ago

https://chatnano.net:7778/

Also, non-SSL server: http://chatnano.net:7779/

utoxin commented 7 years ago

Out of curiosity, I just tried the example client on the Kiwi site, which is SSL, and it works. But it's also on the standard SSL port, so I'm wondering if that's part of it. Somehow.

utoxin commented 7 years ago

This has now expanded to Firefox. Which at least has better dev tools, not that they're helping. The request appears to be almost identical between Firefox (which fails) and Chrome (which works).

This seems like it has to be related to my setup somehow.... but I'm stumped about it. Do you want my config file?

utoxin commented 7 years ago

AHHA! I think I solved it. It may have been something out of date in NPM. I re-ran NPM install, and it seems to have started working for both Firefox and Safari.

utoxin commented 7 years ago

So. False alarm. With the weirdest manifestation ever. Thanks for trying to look at it so fast, and sorry for not thinking about running npm install again after I updated my checkout. It's on my checklist now.