SAP Knowledge Base Article - Preview

3779945 - 403 with empty localservername in ingress logs indicate direct ip access blocked by ingress

Symptom

  • Malicious http requests probing common paths are observed.
  • Ingress/proxy logs show status 403 and empty localservername.

***Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.***


Read more...

Environment

SAP Commerce Cloud

Product

SAP Commerce Cloud all versions

Keywords

ingress, 403, localservername empty, direct ip access, malicious scan, suspicious http requests, phpunit eval-stdin, index.php probing, user agent libredtail-http, commerce cloud, cdn bypass, deny path sets, staging environment, proxy logs, blocked requests , KBA , CEC-SCC-CLA-ENV-EMG , Environment Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.