You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could be nice to brainstorm about how the resource ProxyRule should be defined.
We should be able to :
enable a hostname to target a cargo at specific location using http and https
redirect domain to another eg: www.domain.com -> domain.com
enable tcp / udp to target a specific cargo at specific port
pass extra http header ?
What else should we have ?
This is for now how look look like http and https to target a cargo at specific location:
Http
Resources:
- Name: resource-exampleKind: ProxyRuleConfig:
# List of cargo to watch updatesWatch:
- get-started@globalHttp:
Domain: get-started.comNetwork: Public# Optional SSL configSsl:
Certificate: /path/to/certCertificateKey: /path/to/certDhParam: /path/to/dhparam# Http locationLocations:
- Path: /Target:
# The cargo to target for the locationKey: get-started@globalPort: 9000
Stream
Resources:
- Name: resource-exampleKind: ProxyRuleConfig:
# List of cargo to watch updatesWatch:
- get-started@globalStream:
Network: Public# The protocol to use Tcp | UdpProtocol: TcpPort: 8888# Optional SSL configSsl:
Certificate: /path/to/certCertificateKey: /path/to/certDhParam: /path/to/dhparam# Http locationTarget:
# The cargo to target for the locationKey: get-started@globalPort: 9000
The text was updated successfully, but these errors were encountered:
Could be nice to brainstorm about how the resource ProxyRule should be defined.
We should be able to :
What else should we have ?
This is for now how look look like http and https to target a cargo at specific location:
Http
Stream
The text was updated successfully, but these errors were encountered: