Do HTTPS Reverse Proxies without CONNECT exist? - https

Is it possible to have an HTTPS Reverse Proxy without issuing CONNECT message?
Do those kind of proxies exist?

I found the answer. Not "reverse" proxy but forward proxy is the answer in this case.

Related

Socket.io with YARP

I am trying to build a system using Socket.io and YARP. Yarp is functioning has a Reverse Proxy to all my Services.
When trying establish a connection to my socket.io service, through yarp, I am getting connection_error:
I noticed there are proper configurations used in other Reversed Proxy solutions that are well documented in Socket.io website:
https://socket.io/docs/v4/reverse-proxy/
However, I can't "translate" what they are doing to YARP. Does anyone know if this is possible?
Thanks in advance
I guess stackoverflow was my rubberduck this time...
I checked in postman the request that was being made through my Yarp Server and turns out it wasn't even hitting the correct path. For yarp to connect to a socket.io server you have to use this kind of path in your configuration file:
It seems that a sokcetio request uses it's own path, so you have to make your reverse proxy match the beggining "socket.io/"

How to proxy HTTPS via HTTP without CA or MITM?

HTTP proxy with SSL and DNS support.
I must be lacking some key concepts about proxy-ing because I cannot grasp this. I am looking to run a simply http or https proxy without interfering with SSL. Simply, a fully transparent proxy that can passthrough all the traffic to the browser connected via HTTP or HTTPS proxy without modifying or intercepting any packets. Not able to find any code online or I'm not using the right keywords.
EX. On the browser adding server.someVPN.com:80 on the HTTP proxy field and as soon as you try to visit a website, it prompts for authentication. Then it works perfectly with any domain, any security, any ssl, no further steps needed. Most VPN providers have this.
How's this possible? it even resolves DNS itself. I thought on transparent proxy the dns relies on the client. Preferably looking for a nodeJS solution but any lang works.
Please don't propose any solutions such as SOCKS5 or sock forwarding or DNS overriding or CA based MITM. According to HTTP 1.1 which supports 'CONNECT' this should be easy.
Not looking to proxy specific domains, looking for an all inclusive solution just like most VPN Providers providers.
----Found the answer too quickly, feel free to delete this post/question admins.
The way it works is that the browser knows it is talking to a proxy server, so for example if the browser want to connect to htttp://www.example.com it sends a CONNECT www.example.com:443 HTTP/1.1 to the proxy server, the proxy server resolves wwww.example.com via DNS and then opens a TCP connection to wwww.example.com port 443 and proxies the TCP stream transparently to the client.
I don't know any solution for nodejs. Common proxy servers include Squid, Privoxy and Apache Traffic Server
See also: https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT
Found the solution right after I asked...
This module works perfectly https://github.com/mpangrazzi/harrier
Does exactly what I was asking for.

Is it possible to configure emqttc to use proxy Information

Is it possible to use emqttc https://github.com/emqtt/emqttc when behind a proxy?
You can pass SSL options to the emqttc:start_link function but it doesn't appear to do anything for a proxy. As an example I've tried using {proxy_auth,{Proxy_Username, Proxy_Password}} as an option. Any suggestions on if this is possible or how to configure it for proxy use?
You can not use a HTTP proxy to forward native MQTT connections, they are 2 totally different protocols.
You could forward MQTT over Websockets, but it does not appear that emttc supports MQTT over Websockets.

How to tunnel through HTTP proxy?

Hi my ISP uses proxy authentication to log on to the internet so many of my apps won't work. Is there a way to tunnel all traffic so they're able to connect? Thanks in advance!
You could try a product like Proxifier, it will intercept your app's connections and pipe them through a tunneling http proxy, or SOCKS server.

What is the difference when connecting through a proxy?

I know what a proxy is, and the basics of how they work.
What I was wondering is, what is different in a request that goes through a proxy?
I know when I configure Firefox I simply configure the proxy in a dialog. When I program in python I can use an environment variable.
If I am programming in an environment that doesn't already have support for a proxy, how do I connect through a proxy? Is there an extra header added to requests? Is the protocol slightly different?
The protocol is slightly different. Where a direct connection to example.com would say:
GET /index.html HTTP/1.1
a connection through a proxy would say:
GET http://example.com/index.html HTTP/1.1

Resources