Closed Bug 1739511 Opened 4 years ago Closed 1 year ago

upload speed is throttled going thru Caddy reverse proxy

Categories

(Core :: Networking: Proxy, defect, P2)

Product:
Core
Component:
Networking: Proxy
Version:
Firefox 94
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: vtwintiger, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.9.1

Steps to reproduce:

client has upload bandwidth >100Mbps, server has download bandwidth >100Mbps
This does not happen using Stunnel reverse proxy.
This does not happen on the LAN (HTTP).

  1. configure Caddy on Windows 10 as a reverse proxy for subdomains to serve HTTPS from the local file server (tested apps filebrowser.org, rejetto.com/hfs/)
    Caddy file:
    fileserver.yourdomain.com:8443 {
    reverse_proxy :81
    }

  2. on the Windows 10 x64 desktop client, open Firefox

  3. browse to file server (https://fileserver.yourdomain.com)

  4. start upload cmd, select a large compressed file (e.g., 3GB EXE or 7z)

  5. start the upload - transfer speed hovers around 40Mbps

Actual results:

transfer speed hovers around 40Mbps

Expected results:

Do the same in MS Edge Chromium and you get 100Mbps (as expected based on WAN bandwidth).

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core

So it appears Fx is doing something strange with HTTPS.

Blocks: upload-speed
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged]

This is still happening with the latest Fx and Caddy. Also, what might be a related issue, is that logging into the site (filebrowser, in my case) usually fails the first time.

I'd really like to use Fx, but stuff like this (and slow JS perf) prevents it.

If I understand previous comments correctly:

This does not happen using Stunnel reverse proxy.

This only happens with this proxy.

This does not happen on the LAN (HTTP).

Not using HTTPS doesn't cause this issue?

In the LAN, I do not use HTTPS. I've tried only those two proxies.

Also, for clarity, it seems the file server does not matter (no need to get hung up on filebrowser), as I first saw it with HFS.

Moving bug to Core/Networking: Proxy.

Component: Networking → Networking: Proxy

I think this can be closed now. There was a networking bug fixed a few months (or more) back that fixed this. I tested this workflow today and it worked as expected.

(In reply to Justin from comment #10)

I think this can be closed now. There was a networking bug fixed a few months (or more) back that fixed this. I tested this workflow today and it worked as expected.

Thanks. If you remember which bug it would be nice to track it here.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.