New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reverse_proxy.cd 中有个链接失效了 #220
Comments
@NominationP |
你好,关于nginx反向代理,匹配url有个问题想请教下
这样完全匹配是可以的
https://XXXX/laravel
location /laravel {
proxy_pass http://dockone.io/article;
}
靠参数来找,就失败了,显示 502
https://XXXX/laravel/296
Bad Gateway
location ~* ^/laravel/(.*) {
proxy_pass http://dockone.io/article/$1$is_args$args;
}
2017-09-06 9:50 GMT+08:00 罗泽轩 <notifications@github.com>:
… @NominationP <https://github.com/nominationp>
谢谢纠错。已经把失效的链接指向 Nginx 官方文档上关于 location 的描述了。
http://nginx.org/en/docs/http/ngx_http_core_module.html#location
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK537FlOr-m2q2lHCg9IN61HyDI4qhN0ks5sffppgaJpZM4PMi9y>
.
|
通过日志看到错误 no resolver defined to resolve
然后加了一行 resolver 8.8.8.8; 就好了
之前没看日志就问您是因为日志太满了,根本打不开,又设置了一下日志的路径,才看到。。。。。。。
打扰了!
在 2017年9月6日 下午2:33,ze zhang <zhangze1029@gmail.com>写道:
… 你好,关于nginx反向代理,匹配url有个问题想请教下
这样完全匹配是可以的
https://XXXX/laravel
location /laravel {
proxy_pass http://dockone.io/article;
}
靠参数来找,就失败了,显示 502
https://XXXX/laravel/296
Bad Gateway
location ~* ^/laravel/(.*) {
proxy_pass http://dockone.io/article/$1$is_args$args;
}
2017-09-06 9:50 GMT+08:00 罗泽轩 ***@***.***>:
> @NominationP <https://github.com/nominationp>
> 谢谢纠错。已经把失效的链接指向 Nginx 官方文档上关于 location 的描述了。
> http://nginx.org/en/docs/http/ngx_http_core_module.html#location
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#220 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AK537FlOr-m2q2lHCg9IN61HyDI4qhN0ks5sffppgaJpZM4PMi9y>
> .
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: