virtualGetForm 404 when accessing Aras through Nginx
Hi, I’m running Aras Innovator 14.35.0.44037 behind an Nginx reverse proxy. Setup: Client ↓ HTTPS Nginx ↓ HTTPS :15018 Aras Innovator External URL: https://aras.veconnected.in/VECS_ARAS/ Nginx: location /VECS_ARAS/ { proxy_pass https://127.0.0.1:15018/VECS_ARAS/; proxy_ssl_verify off; proxy_http_version 1.1; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Prefix /VECS_ARAS; proxy_buffering off; proxy_request_buffering off; } Most Aras Client requests work correctly through Nginx and return: status=200 upstream_status=200 However, when opening Item Forms, the following request returns 404: GET /VECS_ARAS/Client/X-salt=3_14.35.0.44037-X/scripts/virtualGetForm? formId=47B8630E2B4C40C1B23C6EE9962F7681& formLastModifiedDate=2025-05-29T19:48:04.24& languageCode=en& itemTypeId=450906E86E304F55A34B3C0D65C097EA& itemTypeLastModifiedDate=2025-05-29T19:44:47.74& databasehash=3a52875cf3d26f02& mode=add Chrome reports: 404 (Not Found) In some cases DevTools reports: 404 (Not Found) (from service worker) Important observations: The same form works when accessed directly from a browser on the Aras VM. Other X-salt resources work correctly through Nginx. Metadata requests and InnovatorServer.aspx requests return 200. I cannot find the virtualGetForm request in the Nginx access log when the client gets the 404. Aras service-worker.js is registered and being served. The problem occurs with multiple forms. Could virtualGetForm be intercepted by the Aras service worker/cache and returning a cached 404? Is there a recommended way in Aras 14.35 to invalidate/reset the client service-worker/cache, or any known Nginx configuration requirements specifically for virtualGetForm?