mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3273] How do route/IP/domain configuration directives work? #2623
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#2623
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 @ylluminate on GitHub (Jan 28, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3273
Bug Description
On an
frpsserver with a well craftedfrps.iniconfiguration file, I am finding a lot of strange traffic that comes in to various attempted efforts to penetrate various file paths, etc.I would like to create specific rules/routes for various inbound garbage that comes into the FRP server, is this possible?
I have seen some various options that seem that
frps.inimight be able to have[route]or[somedomainname.com]with perhaps custom directives such as aredirector multiplecustom_404_pagedirectives...Is there some documentation about these that I'm missing that's not covered in the
https://github.com/fatedier/frp/blob/dev/conf/frps_full.iniexample?frpc Version
0.46.1
frps Version
0.46.1
System Architecture
linux/amd64
Configurations
Any
Logs
No response
Steps to reproduce
...
Affected area
@fatedier commented on GitHub (Jan 29, 2023):
I think you'd better deploy a nginx before frps to achieve your requirements.
frp doesn't support all l7(HTTP) features.
@ADMrugacz commented on GitHub (Feb 4, 2023):
frp docs are confusing
@github-actions[bot] commented on GitHub (Mar 7, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@github-actions[bot] commented on GitHub (Mar 7, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.