O4W and INET_Finalize

Users may also find that they wish to create their own version of INET_FINALIZE, the wrapup routine, to perform any post-processing on the HTML responses.  One common use for an INET_FINALIZE routine is to ensure that, for any secure requests (those that begin with "https://"), any returned html contains only https:// references (mixing http:// and https:// references in the returned document may generate a warning or error on the browser).  One solution when working in an "https://" environment is to ensure that any references in O4W templates or code properly use "https://" as well; another approach is to have a customized INET_FINALIZE with the following code:

* make sure we're HTTPS compliant

if request<HTTP_REFERER$>[1,8] _eqc "HTTPS://" then

  swap "http://" with "https://" in html

  Swap ":433/" With "/" In html

End

Note: It is suggested that you always create a custom, differently-named routine - perhaps initially copied from the provided INET_FINALIZE routine - and replace the INET_FINALIZE entry in the CFG_INET record with the name of the new routine, rather than just changing the provided INET_FINALIZE routine, to avoid the possibility of your custom code being overwritten by updated system routines.