Getting mixed content error when viewing website over HTTPS

because you're loading your assets using http://. To get it to work for both cases, leave off the http: and https:

//domain.com/css/custom.css

Then it will use http or https depending on how it was accessed

Hey Cronix, thanks for the reply. How would I change this? For example, I am referencing stylesheets using blade statements. i.e.

<link rel="stylesheet" href="{{ asset('vendor/bootstrap/css/bootstrap.min.css') }}">

Are you wanting to run your whole site over https, or just parts of it?

5.4 has the helper function secure_asset: https://laravel.com/docs/5.4/helpers#method-secure-asset

The whole website. Ah okay, so I just replace asset with secure_asset and I should be fine?

I'd set up a redirect for all http requests to go to https using .htaccess or in nginx so it can ONLY be accessed via https

Then I'd make your APP_URL set to use https https://yoursite.com

You can also add \URL::forceScheme('https'); to the boot() method of your AppServiceProvider.

After that, asset(), url(), secure_asset(), etc., will all return https

Are you behind a load balancer such as cloudflare?

The issue there is that they terminate the https session before it hits your web server so Laravel thinks the user is requesting http:// and makes links using http

There are several threads on the forum about this problem. Just search for cloud flare

edit: duh moment, I see herokuapp.com in your url. Could be the same issue though.

Cronix, thank you for your answer! I added the code to the boot method and changed the APP_URL, however when I redirected all HTTP to HTTPS by modifying the .htaccess file I was getting an error in my browser ERR_TOO_MANY_REDIRECTS so I didn't change that, but it still works now with the other suggestions!

I was helped

FIX mixed content

At the beginning of the file

/app/Http/routes.php

add:

URL::forceSchema('https');

I'm new here in laracast and im very thankful .. it works tnx Cronix

Hi, I encountered a similar issue and i solved it by following the instructions in the documentation

Note that since this is an issue on heroku, you would have to set proxies to * and headers to Request::HEADER_X_FORWARDED_AWS_ELB

thnx it helped. i should read the documentation more often rather than giving up....lol