I'm trying to troubleshoot an issue for a user of my service https://jsonip.com.
Last week I enabled forcing 301 redirects for all http to https connections.
The user I'm trying to help now was relying on his internal IP being added to the x-forward-for header by his corporate proxy. Now that all connections are being forced to https, it only provides his publicly available IP.
I'm thinking that his corp proxy isn't inserting its own certificate in https connections, so therefore can't inspect the connection and insert/update the x-forward-for header with the proxy IPs.
If so, this is good for the employees' individual privacy (boss can't intercept web traffic) but otherwise is interfering with how the user was using jsonip.com.
Can anyone confirm/deny if my supposition makes sense?