support protocol relative service url

[realies]

at the moment config.yml requires the scheme of the internal service to be specified, this prevents internal services, like reverse proxies, to determine which protocol is used and behave accordingly; can http and https be supported for a single service? e.g. a protocol-relative URL:

tunnel: ***
credentials-file: /home/nonroot/.cloudflared/***.json

ingress:
  - hostname: "*.example.com"
    service: //nginx-proxy-manager

  - service: http_status:404

[0xcryp70]

not possible for a single service, but you can use a single service and handle the rest of it with a reverse proxy or load balancer

[realies]

can you provide an example, @0xcryp70? how would the service know if the origin request was over http or https?

[0xcryp70]

usually with headers like x_forward, it can be handled on headers, like

location / { if ($http_x_forwarded_proto = 'https') { } if ($http_x_forwarded_proto = 'http') { }