3784381 - Custom ICF Handler validation fails after upgrade due to changed ~path_info format

After upgrading to SAP BTP ABAP Environment release 2608, custom ICF service implementations may start returning example errors below, although the same request was processed successfully before the upgrade.:

• HTTP 400 (Bad Request)
• HTTP 404 (Not Found)
• Application-specific validation errors

The issue is typically observed in custom request handlers that retrieve and validate the pseudo-header field ~path_info,

Typical symptoms include:

• Request processing fails after upgrade without any code changes.
• Path comparisons that previously worked no longer match.
• Validation logic rejects requests because the path format differs from previous releases.

• SAP BTP ABAP Environment
• Release 2608 and higher
• Custom ICF services

~path_info, path_info, IF_HTTP_EXTENSION, IF_HTTP_REQUEST, HTTP 400, Bad Request, 2608, Steampunk, leading slash, URL suffix, path validation, custom ICF handler, case sensitive, case insensitive, request URI, pseudo header field, get_header_fields, 3746187   , KBA , BC-MID-ICF , Internet Communication Framework , BC-CST-IC , Internet Communication Manager , BC-MID-UCO , Unified connectivity tooling , Problem