If every page has to check, it looks like the HTTPS environment variable would already show whether HTTPS was used.
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzaie/rzaieenvvar.htm
-----Original Message-----
From: Justin Taylor
Sent: Tuesday, April 21, 2020 12:14 PM
To: 'Web Enabling the IBM i (AS/400 and iSeries)' <web400@xxxxxxxxxxxxxxxxxx>
Subject: RE: [WEB400] Identify http:// connections
So you add that to request responses and then monitor what's coming in? Would each page have to watch for that?
-----Original Message-----
From: B Stone [mailto:bvstone@xxxxxxxxx]
Sent: Tuesday, April 21, 2020 11:01 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WEB400] Identify http:// connections
you could add your own headers to each request to know which one it is.
Inside each virtualhost...
<virtualhost xxxxxx:80>
SetEnv SITE_ENV http
.....
</virtualhost>
<virtualhost xxxxx:443>
SetEnv SITE_ENV https
....
</virtualhost>
Then you can grab the SITE_ENV (or whatever you want to call it) and tell what environment it is.
Bradley V. Stone
www.bvstools.com
GreenTools for PayPal <
https://www.bvstools.com/g4pp.html>: Easily send PayPal invoices from your IBM i applications using RPG ILE! Process refunds, get account balances and more!
As an Amazon Associate we earn from qualifying purchases.