Laravel generate secure https URL from route

Question

Edit

I can't really find a way to generate a secure URL from route name.

To get a full URL, I use

echo route('my_route_name');

But what to do, if I want a URL with https?

Answer 1

UPDATE: As pointed out in the comments, a simpler way of doing this would be adding URL::forceSchema('https'); for Laravel version between 4.2-5.3 or URL::forceScheme('https'); for version 5.4+ in the boot method of your AppServiceProvider file.

Old answer:

It's actually entirely possible and there's only one line of code needed to accomplish that.

Laravel doesn't check the presence of SSL by itself, it depends on Symfony. And there goes our key to making it believe that the current request is secure.

The thing is, we have to set the HTTPS server param to true and the easiest method is to paste the following code in the boot method of your AppServiceProvider:

$this->app['request']->server->set('HTTPS', true);

In my very case, I only need to force SSL in production, the local env should still work on http. This is how I force SSL only on production:

$this->app['request']->server->set('HTTPS', $this->app->environment() != 'local');

By the way, mind those terms, you may need them in the future.

Answer 2

Laravel 8

I recently resolved this by modifying this file:

app/Providers/AppServiceProvider.php

in the method boot() add the following:

URL::forceScheme('https');

Add the use in the top:

use Illuminate\Support\Facades\URL;

to work in your local environment you can leave it like this:

public function boot()
{
    if(env('APP_ENV') !== 'local') {
        URL::forceScheme('https');
    }
}

Note: Don't forget to set your env variable APP_ENV with prod for the production file.

APP_ENV=prod

Answer 3

Actually turns out, that laravel doesn't care if url is secure or not, because it generates based on the current url. If you're on https page, route() will return secure url. If on http, then http:// url

The problem was, that Laravel didn't detect that https was enabled, which was due to faulty server configuration.

You can check if Laravel sees the current connection as https by calling Request::isSecure();

Answer 4

As I mentioned in a relevant question, I found 5 ways of how to generate secure URLs.

1. Configure your web server to redirect all non-secure requests to https. Example of a nginx config:

   server {
       listen 80 default_server;
       listen [::]:80 default_server;
       server_name example.com www.example.com;
       return 301 https://example.com$request_uri;
   }
   

2. Set your environment variable APP_URL using https:

   APP_URL=https://example.com
   

3. Use helper secure_url() (Laravel5.6)

4. Add following string to AppServiceProvider::boot() method (for version 5.4+):

   \Illuminate\Support\Facades\URL::forceScheme('https');
   

5. Implicitly set scheme for route group (Laravel5.6):

   Route::group(['scheme' => 'https'], function () {
       // Route::get(...)->name(...);
   });
   

   At the moment this way is not documented, but it works well.

Answer 5

I think there is only one way to do this.

To generate the secure URL to your named routes, you might want to pass in your route into the secure_url helper function.

secure_url(URL::route('your_route_name', [], false));

You can't really use the route helper function because it generates absolute URL (with http://) by default and it's http not the https version that you wanted

Answer 6

Laravel 5.x will generate secure URL via route() helper if it detects the incoming connection is secure. Problem usually happen if the app is hidden behind load balancer or proxy (e.g. Cloudflare) since the connection between app server and load balancer/proxy might not be secure.

I am using Laravel Forge + Cloudflare now and this is the easiest way I could find to enable app thinking incoming connection is secure (not sure about other proxy).

1. Generate self signed certificate (see https://www.digitalocean.com/community/tutorials/openssl-essentials-working-with-ssl-certificates-private-keys-and-csrs or http://www.selfsignedcertificate.com/)

2. In Forge panel, insert your private key and cert via Sites > your-site > SSL Certificates > Install Existing Certificate.

3. Activate

4. In CloudFlare panel, Crypto > SSL, choose “Full” (not strict)

5. Done (it will take few minutes for the change to get propagated)

In short, connection between client and Cloudflare is secured by Cloudflare's own SSL. Connection between app server and Cloudflare is protected via your generated cert (thus the app is seeing 'connection' as secure.

You can apply the same principle with other stacks.

Answer 7

Use secure_url:

secure_url(URL::route('your_route_name', [], false));

You will need to set URL::route to false in order to not return a full URL. Then use secure_url function generates a fully qualified HTTPS URL to the given path.

From the UrlGenerator interface you can use URL::route

string route(string $name, mixed $parameters = array(), bool $absolute = true)

Get the URL to a named route.
Parameters
string  $name   
mixed   $parameters     
bool    $absolute   
Return Value
string

https://laravel.com/api/5.4/Illuminate/Contracts/Routing/UrlGenerator.html

Answer 8

In most cases routes should be generated with the same scheme your site was loaded with. Laravel automatically detects if request has X-Forwarded-Proto header and uses it to decide which scheme to use in generated route URLs. If your site is behind reverse proxy then you should add reverse proxy IP address to list of trusted proxies. https://github.com/fideloper/TrustedProxy package helps to do this. It's included in Laravel 5.5. For example, my config/trustedproxy.php looks like:

<?php

return [
    'proxies' => '*',

    'headers' => [
    ]
];

I use it with nginx reverse proxy that has the following configuration:

server {
  listen 80;
  server_name example.com; 
  access_log  /var/log/nginx/example.com_access.log;
  error_log   /var/log/nginx/example.com_error.log;

  client_max_body_size 50m;

  location / {
    proxy_pass              http://localhost:8002;
    proxy_set_header        Host $host;
    proxy_set_header        X-Real-IP $remote_addr;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header        X-Forwarded-Proto $scheme;
  }

  listen 443 ssl;
  ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
  include /etc/letsencrypt/options-ssl-nginx.conf;
  ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;


  if ($scheme != "https") {
    return 301 https://$host$request_uri;
  }
}

Replace example.com with your domain. SSL certificates was provided by Let's Encrypt with certbot.

Answer 9

On laravel 5.5.* You only need to add https on your .env file as AppServiceProvider already had function that checks if your APP_URL or app.url on your config has https on it.

class AppServiceProvider extends ServiceProvider
{
 public function boot()
 {

    \URL::forceRootUrl(\Config::get('app.url'));    
    if (str_contains(\Config::get('app.url'), 'https://')) {
        \URL::forceScheme('https');
    }
 }

Answer 10

This is certainly old, but someone like me will dump over here one day.

In your .env file define the APP_URL to use https instead of using http. Because all laravel url are generated based on this variable.

    APP_URL=https://example.com

and wherever you want you can just say

{{ URL::route('my.route', params) }}

Or

{{ route('my.route', params) }}

With make sure all the routes are generated with secure protocol, add in the boot method of AppServiceProvider class:

<?php

namespace App\Providers;

use Illuminate\Routing\UrlGenerator;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot(UrlGenerator $url)
    {
        if (config('app.production')) {
            $url->forceScheme('https');
        }
    }

Answer 11

Just add your application domain with the https protocol in the APP_URL of your .env file.

APP_URL=https://example.com

Then run route:cache

Answer 12

For reference of future visitors:

The secure_url function doesn't correctly handle GET parameters. So, for example, if you want to convert the url that the user has visited into a secure url while retaining the GET fields, you need to use this:

secure_url(Request::path()).'?'.http_build_query(Input::all());

Particularly note the use of path() rather than url() - if you give it a full url, it doesn't replace the http at the start, making it efectively useless.

Answer 13

I came across this issue while trying to generate a route as form action in Blade using Laravel 5.4. Then I hit upon secure_url(), so I tried

{{ secure_url(route('routename', $args)) }} 

This still returned a non-secure URL. :-(

After digging through the code and adding some debug logs, I finally figured out that secure_url does not change the incoming url argument, if it's already an absolute URL (including the scheme).

Fortunately route has an absolute flag as the third argument, and returns a relative URL if $absolute is passed as false.

Assuming /a/{id}/b is a named route "a.b"

route('a.b', 1)        : will return http://[domain]/a/1/b 
route('a.b', 1, false) : will return /a/1/b

Joining the two I arrived at :

{{ secure_url(route('routename', $args, false)) }}

As expected it generated https://[domain]/routeXXX

:-)

Answer 14

I had a problem with redirect trailing slashes after 2 hours of looking for a bug, just need to remove

.htaccess

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)/$ /$1 [L,R=301]

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

to

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

Answer 15

Place this in your filters.php file and everywhere will be forced to https while retaining URL parameters:

//force ssl
App::before(function () {
if(!Request::secure() && App::environment() != 'local')
{
    $baseHost = Request::getHttpHost();
    $requestUri = Request::getRequestUri();
    $newLink = 'https://'.$baseHost.$requestUri;

    return Redirect::to($newLink);
}});

Answer 16

According to the laravel documentation on the url() helper method.

If no path is provided, a Illuminate\Routing\UrlGenerator instance is returned

So you can use the secure method of the UrlGenerator class in the following way:

echo url()->secure('my_route_name');

Answer 17

To generate a secure (https) route use the following built-in 'before' filter called 'auth':

For example:

Route::get('your-route', ['before' => 'auth', 'uses' => YourController@yourAction']);

Now when you output your link it will be prepended with 'https'