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
> For HTTPS we could use SNI to detect hostnames and use for routing but ran into issues with reacting to network changes due to already established TCP tunnels (need some more work to break existing TCP connections when needed).
181
185
186
+
### HTTPS certificate management
187
+
188
+
`krp` uses its own certificate authority (CA) for optional local HTTPS routing.
189
+
- Run `krp https --trust` to create a new certificate and trust it.
190
+
- When HTTPS requests are proxied, `krp` dynamically generates per-host leaf certificates signed by that CA, so each routed hostname gets a valid certificate.
191
+
182
192
## **Running in Docker**
183
193
184
194
To run `krp` in a Docker container, follow these steps:
185
195
186
196
1.**Start Docker Desktop** as an administrator (required for hosts file modification).
0 commit comments