4.15.0/4.16.0: GET request from docker container is automatically modified to use absolute URI

[elerocks]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Actual behavior

GET request coming from inside running container to outside network is translated to GET request with absolute URI.

Expected behavior

Keep the URI relative

Information

• Windows Version: 10
• Docker Desktop Version: 4.15.0
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

• everything has passed

Steps to reproduce the behavior

1. run wireshark
2. run e.g. ubuntu 20.04 container
3. install curl
4. perform "curl www.google.com"
5. observe in wireshark that GET request is: GET www.google.com

• In previous version of docker desktop (4.14.1) it was GET /

This is causing us problems, because we are using third party devices that are unable to handle GET requests with absolute URI.

I've observed this only on windows and only using the latest docker desktop (4.15.0). Others worked fine

[elerocks]

Update: the same issue is happening also with the newest Docker Desktop 4.16.0

Workaround is to disable Automatic Proxy Detection in Windows, but I'm not sure about consequences for customers that might be dependent on this setting.

[jpvanhulst]

I'm having the same issue. Thank you for the temporary workaround.

[elerocks]

Issue still present in 4.16.1 and 4.16.2.

[haydenseitz]

Glad I found this (and duplicate?)! Our fix was to downgrade to v4.12, but I'll try disable the proxy setting as suggested. Thanks for the workaround!

[elerocks]

docker 4.17 partly fixes this issue, but changes the case of headers, e.g. host was changed to Host. Unfortunately this still breaks communication with the third party devices.

Workaround is still the same, disable "Automatic Proxy Detection"

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale