IBM Support

IT17907: INCORRECT SNI HOST HEADER ADDED WHEN USING A PROXY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When DataPower sends a request to a backend service and there is
    a proxy in the topology, the host name of the proxy is set as
    the value of the SNI-Host header instead of the hostname of the
    backend service
    

Local fix

  • Work Around
    
    Configure the SNI host name in the SSL Client Profile.
    1. Set "Use custom SNI Hostname" to 'Yes'
    2. Then enter the desired host name in the "Custom SNI hostname"
    field.
    

Problem summary

  • The TLS extension SNI hostname might incorrectly get set to the
    proxy hostname  when accessing a proxied HTTPS resource.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT17907

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-18

  • Closed date

    2017-01-10

  • Last modified date

    2017-01-18

  • 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

    DATAPOWER

  • Fixed component ID

    DP1234567

Applicable component levels

  • R720 PSY

       UP

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.2"}]

Document Information

Modified date:
25 September 2021