404 Error as prometheus adds a port 443 to my aws app runner domain

[V P]

We want to scrape a https app runner domain without a port number and the Prometheus configuration is according to that. Is there a way to prevent the default port number for https(443) to get applied in the domain name of app runner when the Prometheus targets the https domain?

As my domain https://app-runner.com/actuator/prometheus gets converted to 

https://app-runner.com:443/actuator/prometheus in the targets and gives a 404 error due to the addition on port number in url.

I changed the scheme to https, tried adding 443 port in target field of yml config file as well still getting the same error 404

[Stuart Clark]

I'm not quite sure what you are meaning by "without a port number"? All
connections are to a specific port. If you don't specify a port when
doing a web request it will default to 80 or 443 (depending on if it is
HTTP or HTTPS).

--
Stuart Clark

[V P]

Thanks for the quick reply Stuart, here i am facing an error with app runner domain i.e my app runner service don't include any port in its URL its simply https://example.apprunner.com when m using it with prometheus i.e  https://example.apprunner.com/actuator/prometheus , it taking a default port 443 at  https://example.apprunner.com:443 and thus throwing a 404 error as that's not my actual URL ( https://example.apprunner.com/actuator/prometheus  )