mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #533] url 路由在复用 http 连接时失败 #413
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#413
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sunnyyoung on GitHub (Nov 22, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/533
What version of frp are you using (./frpc -v or ./frps -v)?
What operating system and processor architecture are you using (
go env)?Server:
Configures you used:
Server:
Client:
Steps to reproduce the issue:
以上配置用于穿透局域网内群晖NAS
Test01:
抱歉,您所指定的页面不存在。Test02:
Describe the results you received:
配置中 URL 路由为
/与/*存在冲突Describe the results you expected:
既能访问 www.customdomain.com 的同时也能访问 www.customdomain.com/*
Additional information you deem important (e.g. issue happens only occasionally):
None
Can you point out what caused this issue (optional)
None
@idoall commented on GitHub (Nov 22, 2017):
群晖+docker更好用一些,把frpc设置到docker中如果有其他服务,就新启动一个容器。
如果想外网访问DSM,直接用群晖的DDNS即可
@sunnyyoung commented on GitHub (Nov 22, 2017):
@idoall
群晖内部运行 Docker 的话会影响到休眠吧?这个比较不可控,因此我的 frpc 是放在路由器上的(软路由)
我没有公网IP,DDNS这个不行,群晖提供的 QuickConnect 速度太慢了
@idoall commented on GitHub (Nov 23, 2017):
不会休眠,我的网站就是这样挂的,你用阿里云的ddns,不用群晖自己的
@fatedier commented on GitHub (Dec 7, 2017):
url 路由目前只解析每一个连接的第一个请求。浏览器对于同一个域名的请求可能会复用连接,所以同一个连接中的后续请求不会再被转发。这个目前还没有太好的解决方法,之后考虑下要怎么优化。
@fatedier commented on GitHub (Dec 15, 2017):
0.14.1 版本优化 http 类型的 proxy,可以尝试下。
@sunnyyoung commented on GitHub (Dec 17, 2017):
@fatedier 访问已正常,感谢!
@sunnyyoung commented on GitHub (Dec 21, 2017):
貌似
HTTPS的复用也有上述问题呃