mike_henden

It gets weirder — according to console navscript.js IS loading… ??!! So in answer to your comment @nightjarnz there is NO error ??

mike_henden

That’s right @nightjarnz … the thing is that http://Page.ss and http://HomePage.ss are on the same level, then we have the template folder containing other page types… none of which have the required .js file loading ??

nightjarnz

suggest you'll find a console error in the other page types :>

nightjarnz

so it's on the main http://Page.ss 'main' template?

mike_henden

@nightjarnz — that’s the really weird thing… no, the script is NOT on http://HomePage.ss… and yet it’s running there…

halles

> “X-Forwarded-Proto” < This is how heroku provides the info

halles

Among other bits: > SS_TRUSTED_PROXY_PROTOCOL_HEADER = “X-Forwarded-Proto” This makes SS use that protocol regardless of the lack of HTTPS/SSL on the current request.

nightjarnz

where Page is the parent class, and the parent of all other subclasses.

MichalKleiner

for local SSLs we use https://github.com/paulczar/omgwtfssl in docker-compose controlled stack of containers and though the certs are not trusted, they are better than no certs 😄

Show 1 attachment(s)
paulczar/omgwtfssl

SSL certificate generation for developers who don't TLS good

Hide attachment content
nightjarnz

@mike_henden sounds like you've put the script in the http://HomePage.ss, yes?