vendor assets and SSL

[flinguin]

since the protocol for our staging environment was switched from http to https all the cruddy assets in the backend get blocked by the browser because they still are requested via http.

is there anything to be done after switching to https - couldn't find anything in the docs or the cruddy config file.

thanks

[flinguin]

found out a little bit more info:
in our case the ssl-connection is terminated at a reverse proxy (nginx) the request is then internally forwarded via http to the staging server. the js files of the backend and also most of the links in the Cruddy-json variable are generated absolute depending on the request ... so they all look like "http://domain/..."

i don't know if absolute urls are really needed or if site-relative urls or even just urls without the protocoll wouldn't be better. on the other hand i couldn't yet figure out a way to tell laravel or cruddy to render the pages not with the requested protocoll/domain but to force a protocoll and domain for rendering.

[lazychaser]

Hmm, will figure it, maybe add config entry secure, you can alter CruddyServiceProvider to use secure_asset instead of asset for now