IBM Support

PH64800: NEED SOMETHING LIKE "HTTPSINDICATORHEADER" FOR IBM HTTP SERVER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as new function.

Error description

  • Need something like "httpsIndicatorHeader" for IBM HTTP Server
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM HTTP Server                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Force request to be treated as HTTPS    *
    *                      for                                     *
    *                      TLS offload in front of IHS             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When HTTPS is conditionally terminated in front of IHS, there is
    no flexible way to tell IHS that the HTTPS scheme (protocol) was
    originally used.
    

Problem conclusion

  • A new internal per-request environment variable
    "ihs-force-https" can be set to any value to direct IHS to treat
    the current requests scheme (protocol) as HTTPS.
    
    This behavior is similar to adding the optional second argument
    to the Listen directive, but configurable per-request.
    
    The changing of the internal representation of the scheme to
    https has the following noteworthy effects:
    1. The WAS WebServer Plug-in will default to using a TLS
    connection to the backend server.
    2. Self-referential URL's generated by the
    webserver or application server will use the https://
    scheme, maintaining the clients use of HTTPS
    3. When the default port (443) is used, virtual
    host mapping inside of the WAS WebServer Plug-in and the
    application server will use port 443 instead of 80.
    
    An example of setting the variable conditionally:
    
    SetEnvIf X-Forwarded-Proto ^https$ ihs-force-https=1
    
    
    The fix for this APAR is targeted for inclusion in IBM HTTP
    Server fix packs 9.0.5.24. For more information,
    see 'Recommended Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH64800

  • Reported component name

    IBM HTTP SERVER

  • Reported component ID

    5724J0801

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-01-13

  • Closed date

    2025-05-07

  • Last modified date

    2025-07-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IBM HTTP SERVER

  • Fixed component ID

    5724J0801

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTJ","label":"IBM HTTP Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 July 2025