HTTP & HTTPS on frp

Modify HTTP Request Header

Mon, 01 Jan 0001 00:00:00 +0000

Modify Host Header

Normally, frp will not modify any forwarded data. However, some backend services will display different websites based on the Host field in HTTP request headers, such as nginx’s virtual host service. Enabling the Host Header modification feature can dynamically modify the Host field in HTTP requests. Note that this feature is only available for HTTP type proxies.

# frpc.toml
[[proxies]]
name = "web"
type = "http"
localPort = 80
customDomains = ["test.yourdomain.com"]
hostHeaderRewrite = "dev.yourdomain.com"

The original Host field test.yourdomain.com in the HTTP request will be replaced with dev.yourdomain.com when forwarded to the backend service.

Set BasicAuth Authentication

Mon, 01 Jan 0001 00:00:00 +0000

Since all clients share one frps HTTP service port, anyone who knows your domain name and URL can access your services deployed in the intranet. However, in some scenarios, you need to ensure that only limited users can access.

frp supports protecting your web services through HTTP Basic Auth, requiring users to access your services through username and password.

This feature is currently limited to HTTP type proxies and requires adding username and password settings in frpc’s proxy configuration.

Custom Subdomain

Mon, 01 Jan 0001 00:00:00 +0000

When multiple people are using one frps simultaneously, using custom subdomains is more convenient.

By configuring subdomainHost in frps’s configuration file, you can enable this feature. After that, in frpc’s http and https type proxies, you can configure a subdomain parameter instead of configuring customDomains.

You only need to resolve *.{subdomainHost} to the server where frps is located. After that, users can specify their own subdomain for their web services through subdomain, and access their web services through {subdomain}.{subdomainHost}.

Routing

Mon, 01 Jan 0001 00:00:00 +0000

URL Routing

frp supports routing and forwarding to different backend services based on the URL path of the request.

Specify one or more URL prefixes that a proxy can match through the locations field in the configuration file (currently only supports maximum prefix matching, regex matching will be considered later). For example, specifying locations = "/news" means all requests with URLs starting with /news will be forwarded to this service.