Environment: SAP S/4HANA Cloud (Public Edition) 3-System Landscape, utilizing Developer Extensibility via Eclipse ADT.
Context: A custom backend HTTP handler is active, published, and successfully responds to direct browser requests (GET and POST) with status codes.
The Symptom: When running the custom SAP UI5 application locally via Business Application Studio (npm run start) after removing the local ui5.yaml proxy backend destination, relative fetch calls fail with a browser console error (404 Cannot POST or 405 Method Not Allowed). The local server attempts to route the request through its own host URL under a /test/ or local path context rather than proxying it securely to the public cloud tenant (my437226.s4hana.cloud.sap).
Expected Behavior: Local preview environments should seamlessly route service calls or provide native configuration guidelines for handling absolute routing and testing custom HTTP handlers without requiring local BAS proxy destinations that clash with standard public cloud deployment paradigms.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.