Issues with http basic auth on the client side

[hugows]

Hi guys,

I think I arrived at an interesting problem - I wish I could understand it better.

Let me define the parts:

a. server.go: runs on hugows.com, a linux vps
b. client.go: runs on my windows pc, in home network, exposing the android app (192.168.0.10)
c. android: local client runs on my home network (w/ Wireless mic app) (192.168.0.20)
d. outsider: a browser connecting to hugows.com:9999

Now, this android application has HTTP Basic Auth. I see the following pattern, with both Go apps running:

1. outsider open hugows.com:9999; http response seems to hang indefinitely
2. if I kill client.go, finally it popups up asking for auth details. If I enter then I receive the expeced error from server.go (could not connect to client or something - client is not running now)
3. If I run client.go again then:
4. outsider can properly open the page!!!

Sorry I couldn't explain it better...

[mmatczuk]

Hi @hugows,
could you please attach logs and a client / server configs.

[hugows]

Sorry, how could I produce logs?
Client/server just like the main page example.

[rjeczalik]

@hugows There's no auth forwarding in tunnel. What would help is to allow for custom handler that serves new session (the one that does CONNECT and then hijacks the tcp conn). There was an idea to provide a different implementation than CONNECT (e.g. use tls handshake instead) since most enterprise proxies block CONNECT requests (or public wifis) and it makes tunnel also not work for such use-cases.