blocks|key|4165318|text|好的，我知道了。希望这能对未来的人有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4165319|看起来Laravel忽略了http请求的url文件中的config\app.php属性(它确实声明它只用于手工)，而是使用HTTP_HOST或SERVER_NAME为URL生成域。|offset|length|style|CODE|4165320|若要重写此默认url，请转到您的routes.php文件并使用以下方法：|4165321|URL::forceRootUrl('http://subdomain.newurl.com');|code-block|syntax|javascript|4165322|这将迫使URL生成器使用新的url而不是HTTP_HOST或SERVER_NAME值。|4165323|entityMap^0|0|K|3|R|E|1P|9|1Z|B|0|G|A|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$]]

Ok, so I got it. Hopefully this will help someone in the future.

It seems like Laravel ignores the <code>url</code> property in the <code>config\app.php</code> file for http requests (it does state it's only for artisan), and it instead uses either <code>HTTP_HOST</code> or <code>SERVER_NAME</code> provided by apache to generate the domain for URLs.

To override this default url, go to your <code>routes.php</code> file and use the following method:

<pre><code>URL::forceRootUrl('http://subdomain.newurl.com');
</code></pre>

This will then force the URL generator to use the new url instead of the HTTP_HOST or SERVER_NAME value.

blocks|key|4658682|text|当Laravel+5应用程序没有意识到SSL负载均衡器的背后时，我遇到了同样的问题(或类似的问题)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4658683|我有以下设计：|4658684|客户端通过HTTPS与SSL负载均衡器进行通信。|unordered-list-item|4658685|SSL负载均衡器通过HTTP与后端服务器对话|4658686|但是，这会导致使用http://+schema生成HTML代码中的所有URL。|4658687|下面是一个快速的‘n’脏解决方案，以实现此工作，包括架构(http+vs.+.+https)：|4658688|将以下代码放在app/Http/routes.php之上|offset|length|style|BOLD|4658689|在最新版本的laravel中，使用web/routes.php|4658690|$proxy_url++++=+getenv('PROXY_URL');
$proxy_schema+=+getenv('PROXY_SCHEMA');

if+(!empty($proxy_url))+{
+++URL::forceRootUrl($proxy_url);
}

if+(!empty($proxy_schema))+{
+++URL::forceSchema($proxy_schema);
}|code-block|syntax|javascript|4658691|然后将以下行添加到.env文件中：|4658692|PROXY_URL+=+http://igateway.somedomain.com|4658693|如果您还需要将生成的HTML代码中的模式从http://更改为，只需添加以下行：|4658694|PROXY_SCHEMA+=+https|4658695|在最新版本的laravel中，forceSchema方法名已更改为forceScheme，上面的代码应该如下所示：|CODE|4658696|if+(!empty($proxy_schema))+{
++++URL::forceScheme($proxy_schema);
}|4658697|entityMap^0|0|0|0|0|0|0|7|J|0|H|E|0|0|9|4|0|0|V|9|0|0|0|1L|F|B|X|B|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1G|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1H|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1I|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1J|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1K|8|@$O|1L|P|1M|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1N|8|@$O|1O|P|1P|Q|R]]|9|@]|A|$]]|$1|U|3|V|5|W|7|1Q|8|@]|9|@]|A|$X|Y]]|$1|Z|3|10|5|6|7|1R|8|@$O|1S|P|1T|Q|R]]|9|@]|A|$]]|$1|11|3|12|5|W|7|1U|8|@]|9|@]|A|$X|Y]]|$1|13|3|14|5|6|7|1V|8|@$O|1W|P|1X|Q|R]]|9|@]|A|$]]|$1|15|3|16|5|W|7|1Y|8|@]|9|@]|A|$X|Y]]|$1|17|3|18|5|6|7|1Z|8|@$O|20|P|21|Q|R]|$O|22|P|23|Q|19]|$O|24|P|25|Q|19]]|9|@]|A|$]]|$1|1A|3|1B|5|W|7|26|8|@]|9|@]|A|$X|Y]]|$1|1C|3|-4|5|6|7|27|8|@]|9|@]|A|$]]]|1D|$]]

I ran into the same (or similar problem), when a Laravel 5 application was not aware of being behind an SSL load-balancer.

I have the following design:

<ul>
<li>client talks to an SSL load balancer over HTTPS</li>
<li>SSL load balancer talks to a back-end server over HTTP</li>
</ul>

That, however, causes all the URLs in the HTML code to be generated with http:// schema.

The following is a quick'n'dirty workaround to make this work, including the schema (http vs. https):

Place the following code on top of app/Http/routes.php

In latest version of laravel, use web/routes.php

<pre><code>$proxy_url = getenv('PROXY_URL');
$proxy_schema = getenv('PROXY_SCHEMA');

if (!empty($proxy_url)) {
 URL::forceRootUrl($proxy_url);
}

if (!empty($proxy_schema)) {
 URL::forceSchema($proxy_schema);
}
</code></pre>

then add the following line into .env file:

<pre><code>PROXY_URL = http://igateway.somedomain.com
</code></pre>

If you also need to change schema in the generated HTML code from http:// to https://, just add the following line as well:

<pre><code>PROXY_SCHEMA = https
</code></pre>

In latest version of laravel <code>forceSchema</code> method name has changed to <code>forceScheme</code> and the code above should look like this:

<pre><code>if (!empty($proxy_schema)) {
 URL::forceScheme($proxy_schema);
}
</code></pre>

blocks|key|4165379|text|看来Laravel有更方便的解决方案。核对答案：termination)?|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4165380|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/29992233/how-do-i-configure-ssl-with-laravel-5-behind-a-load-balancer-ssl-termination^0|O|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Seems the Laravel have more convinient solution.. Check answer there: <a href="https://stackoverflow.com/questions/29992233/how-do-i-configure-ssl-with-laravel-5-behind-a-load-balancer-ssl-termination">How do I configure SSL with Laravel 5 behind a load balancer (ssl_termination)?</a>

blocks|key|793187|text|以下是@TimeLord的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|793188|在最新版本的laravel中，强制模式的名称已经更改，现在是：URL::forceScheme()|offset|length|style|CODE|793189|entityMap^0|0|V|I|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Following up @TimeLord's solution:

In latest version of laravel the name for forced schema has changed and now it is:
<code>URL::forceScheme()</code>

blocks|key|4165419|text|我知道这个话题是旧的a.f，但我一直在解决这个问题，在我的DatabaseSessionHandler.pdf+@照明/会话中替换了下面一行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4165420|++++protected+function+ipAddress()
++++{
++++++++return+$_SERVER['HTTP_X_FORWARDED_FOR'];
//++++++++return+$this->container->make('request')->ip();
++++}|code-block|syntax|javascript|4165421|当然，您需要首先迁移sesssion表并设置配置。|4165422|(.env变量SESSION_DRIVER=database)|4165423|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I know this topic is old a.f but I've been solving this issue by replacing the following line in my DatabaseSessionHandler.pdf [@Illuminate/Session]:

<pre><code> protected function ipAddress()
 {
 return $_SERVER['HTTP_X_FORWARDED_FOR'];
// return $this-&gt;container-&gt;make('request')-&gt;ip();
 }
</code></pre>

Of course you need to migrate the sesssion table first and set up the config 
(.env Variable SESSION_DRIVER=database)

blocks|key|4658783|text|转到app/Http/中间件/TrustProxies.php并更改受保护的变量$proxies，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4658784|protected+$proxies+=+['127.0.0.1'];|code-block|syntax|javascript|4658785|就这个！开心点！|4658786|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Go to app/Http/Middleware/TrustProxies.php and change the protected variable $proxies like this:
<pre><code>protected $proxies = ['127.0.0.1'];
</code></pre>
Just this! Be happy!

blocks|key|4658798|text|在App\Providers\AppServiceProvider类中添加此代码|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4658799|if+(Str::contains(Config::get('app.url'),+'https://'))+{
++++URL::forceScheme('https');
}|code-block|syntax|javascript|4658800|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

add this code in App\Providers\AppServiceProvider class
<pre><code>if (Str::contains(Config::get('app.url'), 'https://')) {
 URL::forceScheme('https');
}
</code></pre>

blocks|key|4658815|text|对于nginx来说，你不需要在Laravel做任何额外的事情。修复可以在从nginx配置；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4658816|server+{
++++listen+80;
++++listen+[::]:80+ipv6only=on;

++++server_name+sub.domain.dev;

++++location+/+{
++++++++proxy_set_header+X-Real-IP+$remote_addr;
++++++++proxy_set_header+Host++sub.domain.dev;
++++++++proxy_set_header+X-Forwarded-For+$proxy_add_x_forwarded_for;
++++++++proxy_pass+http://127.0.0.1:8000;
++++}
}|code-block|syntax|javascript|4658817|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For nginx, you don't need to do anything extra in Laravel. The fix can be done at from nginx config;
<pre><code>server {
 listen 80;
 listen [::]:80 ipv6only=on;

 server_name sub.domain.dev;

 location / {
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header Host sub.domain.dev;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_pass http://127.0.0.1:8000;
 }
}
</code></pre>

blocks|key|4658864|text|因为laravel路由不是从config/app本身创建的，而是从服务器创建的。我的解决方案是将proxy_set_header主机添加到nginx的配置中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4658865|server+{
++++listen+80;
++++server_name+my.domain.com;

++++location+/+{
++++++++proxy_set_header+X-Real-IP+$remote_addr;
++++++++proxy_set_header+Host++my.domain.com;
++++++++proxy_set_header+X-Forwarded-For+$proxy_add_x_forwarded_for;
++++++++proxy_pass+http://127.0.0.1:8000;
++++}+
}|code-block|syntax|javascript|4658866|我用的是在机器上运行的nginx内部有nginx码头的laravel+8，所以是双nginx。|4658867|entityMap^0|E|A|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Because laravel route is created not from the <code>config/app</code> itself rather than from the server. My solution is adding the proxy_set_header Host to the nginx's config.
<pre><code>server {
 listen 80;
 server_name my.domain.com;

 location / {
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header Host my.domain.com;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_pass http://127.0.0.1:8000;
 } 
}
</code></pre>
i'm using laravel 8 with nginx docker inside a running nginx on the machine, so yeah it's double nginx

blocks|key|4658924|text|想出一种更干净的方法，只做负载平衡器告诉它的事情，将这个函数添加到您的RouteServiceProvider中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4658925|protected+function+enforceProtocol()
{
++++if(request()->server->has('HTTP_X_FORWARDED_PROTO')){
++++++++URL::forceScheme(request()->server()['HTTP_X_FORWARDED_PROTO']);
++++}
}|code-block|syntax|javascript|4658926|在引导部分中，简单地将其调用如下|4658927|public+function+boot()
{
++++$this->enforceProtocol();
++++//other+stuff
}|4658928|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Figured out a way that much cleaner and only does exactly what the loadbalancer tells it to, add this function to your RouteServiceProvider
<pre><code>protected function enforceProtocol()
{
 if(request()-&gt;server-&gt;has('HTTP_X_FORWARDED_PROTO')){
 URL::forceScheme(request()-&gt;server()['HTTP_X_FORWARDED_PROTO']);
 }
}
</code></pre>
and in the boot section, simple call it like so
<pre><code>public function boot()
{
 $this-&gt;enforceProtocol();
 //other stuff
}
</code></pre>

Ok, so for development purposes, we have a dedicated web server. It's not currently connected directly to the internet, so I've setup an apache reverse proxy on another server, which forwards to the development server.

This way, I can get web access to the server.

The problem is, the routes in Laravel are now being prefixed with the internal server IP address, or the servers computer name.

For example, I go to <a href="http://subdomain.test.com">http://subdomain.test.com</a> but all the routes, generated using the <code>route()</code> helper, are displaying the following url: <code>http://10.47.32.22</code> and not <code>http://subdomain.test.com</code>.

The reverse proxy is setup as such:

<pre><code>&lt;VirtualHost *:80&gt;
 ServerName igateway.somedomain.com

 ProxyRequests Off
 &lt;Proxy *&gt;
 Order deny,allow
 Allow from all
 &lt;/Proxy&gt;

 ProxyPass / http://10.47.32.22:80/
 ProxyPassReverse / http://10.47.32.22:80/
 &lt;Location /&gt;
 Order allow,deny
 Allow from all
 &lt;/Location&gt;
&lt;/VirtualHost&gt;
</code></pre>

I have set the actual domain name in <code>config\app.php</code>. 

Question

How can I set the default URL to use in routing? I don't want it using the internal addresses, because that defeats the point of the reverse proxy. 

I've tried enclosing all my routes in a <code>Route::group(['domain' ...</code> group, which doesn't work either.

Laravel routes behind reverse proxy

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

好的，为了开发目的，我们有一个专用的web服务器。它目前没有直接连接到internet，所以我在另一台服务器上设置了一个apache反向代理，该服务器转发给开发服务器。这样，我就可以访问服务器。问题是，Laravel中的路由现在以内部服务器IP地址或服务器计算机名作为前缀。例如，我转到，但是使用route()助手生成的...

问反向代理背后的Laravel路由
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问反向代理背后的Laravel路由EN