Hi. We're developing an extension for an existing embedded hardware.
The device does not offer SSL but communicates with a server through HTTP.
We're building a hardware extension that acts as a HTTPS proxy with offloading of the SSL/TLS functionalitiy.
The device sends HTTP packets, our hardware extension (running Linux on arm) converts this to a HTTPS connection.
All SSL functions are done in the extension.
I figured it should work with nginx Proxy/ReverseProxy functionality.
So far I only came accross redirection which again gives the device a https url which it can't handle.
One idea would be that the extension is the http endpoint, unpacks the data and packs it again in HTTPS.
The extension should act as the only client that talks directly to the server.
This is basically the reverse view of "regular" ssl offloading done as a load balancing function.
I would really appreciate some help or some direction to look at.
Thanks
The device does not offer SSL but communicates with a server through HTTP.
We're building a hardware extension that acts as a HTTPS proxy with offloading of the SSL/TLS functionalitiy.
The device sends HTTP packets, our hardware extension (running Linux on arm) converts this to a HTTPS connection.
All SSL functions are done in the extension.
I figured it should work with nginx Proxy/ReverseProxy functionality.
So far I only came accross redirection which again gives the device a https url which it can't handle.
One idea would be that the extension is the http endpoint, unpacks the data and packs it again in HTTPS.
The extension should act as the only client that talks directly to the server.
This is basically the reverse view of "regular" ssl offloading done as a load balancing function.
I would really appreciate some help or some direction to look at.
Thanks