Post AlXPLlWITfIN5Dfdqa by teidesu@very.stupid.fish
 (DIR) More posts by teidesu@very.stupid.fish
 (DIR) Post #AlXPLlWITfIN5Dfdqa by teidesu@very.stupid.fish
       2024-08-31T20:45:02.643Z
       
       0 likes, 0 repeats
       
       is there a single reason not to use CONNECT when using http proxies? even if i indeed proxy plain http traffic, not doing that seems too much of an abstraction leak lolwikipedia mentions that Since all traffic is encapsulated inside normal GET and POST requests and responses, this approach works through most proxies and firewallsbut like, it's still not a "normal" GET/POST, normal http requests don't start with a protocol :/
       
 (DIR) Post #AlXPLmTquEvy3vXCfw by teidesu@very.stupid.fish
       2024-08-31T20:46:59.034Z
       
       0 likes, 0 repeats
       
       i see that curl does avoid using CONNECT unless neededbut if im implementing a general-purpose tcp proxy layer, it seems like just ignoring anything except CONNECT is the way to go, esp considering that 99.9% servers should still support CONNECT (for https at least)bc otherwise i'd have to sniff the content before establishing the connection ​:neocat_googly_woozy:​
       
 (DIR) Post #AlXPLnPdRP9ex8ZLk0 by chayleaf@fedi.pavluk.org
       2024-08-31T21:00:57.048110Z
       
       0 likes, 0 repeats
       
       @teidesu CONNECT is easier to implement but it's preferable for clients to not use it - that way the proxy has more flexibility and can easily do stuff like caching or any other processing. Actually, you don't even have to use CONNECT for https, clients just do it for security.Proxies actually have a wide range of use, some good, some bad, it's just that https made them more or less worthless for all purposes but just raw proxying, unless you wanna add your root cert to all the machines using the proxy.