Opened 12 months ago

Closed 4 months ago

Last modified 4 months ago

#2338 closed defect (fixed)

I2P router makes multiple requests through outproxy while its disabled

Reported by: anonymous maybe Owned by:
Priority: minor Milestone: 0.9.41
Component: apps/i2ptunnel Version: 0.9.37
Keywords: Cc:
Parent Tickets: #2540 Sensitive: no

Description

i have disabled the 4444,4445 clearnet connect ability but it will show inside the status messages here http://127.0.0.1:7657/i2ptunnel/list multiple time of outproxy requests:

No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
Client ready, listening on 127.0.0.1:6668, delaying tunnel open until required
Tunnels ready for client: Standard client on 127.0.0.1:7659
Client ready, listening on 127.0.0.1:7659
Tunnels ready for client: Standard client on 127.0.0.1:7660
Client ready, listening on 127.0.0.1:7660
Tunnels ready for client: HTTPS Proxy on 127.0.0.1:4445
Client ready, listening on 127.0.0.1:4445
Configuration changes saved
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
No outproxy found for the request.
Configuration changes saved

isnt by disabiling it enough to stop the request or something im not getting?

what is the thing which making the request that much to the outproxy?

Subtickets

Change History (8)

comment:1 Changed 12 months ago by anonymous maybe

Summary: I2P router makes multiple requests through outproxyI2P router makes multiple requests through outproxy while its disabled

comment:2 Changed 12 months ago by Eche|on

Status: newtesting

Ok, did you disable the proxy at whole, which renders this a normal behaviour, or did you remove the http settings for outproxy only?

comment:3 Changed 12 months ago by anonymous maybe

only removed the outproxy ability , but the tunnel itself is still working for i2p domains browsing.

comment:4 Changed 12 months ago by zzz

Milestone: undecided0.9.38
Status: testingneeds_work

Interesting. We probably should adjust the logging for this. The actual requests are almost certainly coming from your browser. The router itself should not ever request clearnet resources through the proxy. So the theory - in the title of this ticket - doesn't sound right.

comment:5 Changed 11 months ago by anonymous maybe

So what more logging or how to do more logging on this ?

comment:6 Changed 4 months ago by anonymous maybe

Parent Tickets: 2540
Sensitive: unset

comment:7 Changed 4 months ago by zzz

Milestone: 0.9.380.9.41
Resolution: fixed
Status: needs_workclosed

Removed log to i2ptunnel status window
Added URL to router log message (log level WARN for I2PTunnelHTTPClient or I2PTunnelConnectClient) in 3775252ce316946d292de6944621c54f666d2c0b to be 0.9.40-12

For the theory that i2ptunnel is somehow using the outproxy even when disabled, see discussion in #2540

comment:8 Changed 4 months ago by anonymous maybe

dded URL to router log message (log level WARN for I2PTunnelHTTPClient or I2PTunnelConnectClient) in 3775252ce316946d292de6944621c54f666d2c0b to be 0.9.40-12

Hope this can help as well:

    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Setting host = nrbnshsndzb6homcipymkkngngw4s6twediqottzqdfyvrvjw3pq.b32.i2p
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[Accept-Language: en-US,en;q=0.5]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[Accept-Encoding: gzip, deflate]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[Connection: keep-alive]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[Upgrade-Insecure-Requests: 1]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Line=[]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: NewRequest header: [GET /index.php?title=Plugins HTTP/1.1
         Host: nrbnshsndzb6homcipymkkngngw4s6twediqottzqdfyvrvjw3pq.b32.i2p
         Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
         Accept-Encoding: gzip, deflate
         Upgrade-Insecure-Requests: 1
         X-Accept-Encoding: x-i2p-gzip;q=1.0, identity;q=0.5, deflate;q=0, gzip;q=0, *;q=0
         User-Agent: MYOB/6.66 (AN/ON)
         Connection: close
        
         ]
    6/18/19, 7:02:16 PM DEBUG [nt Runner 10] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/25]: Destination: i2pwiki.i2p
    6/18/19, 8:23:43 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/28]: Line=[CONNECT location.services.mozilla.com:443 HTTP/1.1]
    6/18/19, 8:23:43 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/28]: First line [CONNECT location.services.mozilla.com:443 HTTP/1.1]
    6/18/19, 8:23:43 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: Before selecting outproxy for location.services.mozilla.com:443
    6/18/19, 8:23:43 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: After selecting outproxy for location.services.mozilla.com:443: null
    6/18/19, 8:23:43 PM WARN [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/28]: Host wants to be outproxied, but we dont have any!
    6/18/19, 8:23:44 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/29]: Line=[CONNECT shavar.services.mozilla.com:443 HTTP/1.1]
    6/18/19, 8:23:44 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/29]: First line [CONNECT shavar.services.mozilla.com:443 HTTP/1.1]
    6/18/19, 8:23:44 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: Before selecting outproxy for shavar.services.mozilla.com:443
    6/18/19, 8:23:44 PM DEBUG [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: After selecting outproxy for shavar.services.mozilla.com:443: null
    6/18/19, 8:23:44 PM WARN [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/29]: Host wants to be outproxied, but we dont have any!

specifically:

6/18/19, 8:23:43 PM WARN [nt Runner 12] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/28]: Host wants to be outproxied, but we dont have any!
Note: See TracTickets for help on using tickets.