-
**Problem Description**
SonarCloud has identified a security vulnerability in our Docker Compose setup due to the use of HTTP. It recommends transitioning to HTTPS to enhance security, though this …
-
--http-peer-addr arguement doesn't work as expected
When I use --http-peer-addr the get address should be replaced by toto.my.domain.com but it isn't the case, in debug mode it is still the ip adre…
-
I ran into an issue today where using `fetch()` would fail because the destination web server was mis-behaving with `HTTP/2` requests.
Using `HTTP 1.0/1.1` via command line works fine, but neither…
-
**Is your feature request related to a problem? Please describe.**
We already have an TCP handling of ha-proxy-protocol, but still not support HTTP/HTTPS.
In our case, we want to parse ha-proxy prot…
-
**Is your feature request related to a problem? Please describe.**
Near as I can tell, when using the com.azure.core.http client, you can only select between HTTP/1.1 and HTTP/2 by using one of the c…
-
# Why?
Native protocol has a lot of advantages:
1. Serialization doesn't require escaping special characters
2. DBMS resources utilization much more efficient
3. Single TCP connection per client f…
-
### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
Using OpenAI models with assistant. Retrying will sometimes work.
### Environment
Zed: v0.155.2 …
-
# Bug Report
## Describe the Bug
On https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol, below the about text the given link "https://eclipse.dev/dataspace-protocol-base" leads …
-
When using ClientRequestInterceptor with ProxyAgent, it ends with error
TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
at new ClientRequest (node:_http_clie…
-
http protocol is hardcoded for dev server
for production there is app.listen that is wrapper over http.listen
https support required for dev & production