<![CDATA[Is netsh http add urlacl still required for HTTPS port binding with the integrated Kestrel web server]]>

<![CDATA[Is netsh http add urlacl still required for HTTPS port binding with the integrated Kestrel web server]]>Hi,

Using Proget 2026 with Postgres and Kestrel.

The HTTPS Support docs say that binding the integrated web server to a port below 1024 requires a URL reservation
https://docs.inedo.com/docs/installation/windows/web/https-support#https-binding-to-a-port-recommended

Example:
netsh http add urlacl url=https://*:443/ user="NETWORK SERVICE"

My understanding is that URL reservations (urlacl) only apply to HTTP.sys listeners (HttpListener/IIS).

Since the integrated web server now runs on Kestrel and not IIS, the reservation isn't needed.
Is that correct, and is the urlacl step a leftover from the earlier HttpListener/IIS-based server?

]]>https://forums.inedo.com/topic/5844/is-netsh-http-add-urlacl-still-required-for-https-port-binding-with-the-integrated-kestrel-web-serverRSS for NodeTue, 22 Sep 2026 22:26:30 GMTTue, 22 Sep 2026 13:11:22 GMT60