https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idi-p/1633116 <P>During local development the experience is hosted on <A href="https://localhost:3001" target="_blank">https://localhost:3001</A> per the typical ExB installation and our backed API is hosted on <A href="https://localhost" target="_blank">https://localhost</A>&nbsp;(or another domain). However, the Integration, Acceptance, and Production frontend and backend deployments are all deployed on the <U>same domain</U>, e.g., <A href="https://mydomain.com/myapp" target="_blank">https://mydomain.com/myapp</A>.</P><P>When calling our custom backend API we use known relative paths — e.g.,&nbsp;fetch("api/weather") — as we prefer convention over configuration. However, this isn't workable as without a proxy the frontend sends requests to <A href="https://localhost:3001/api/weather" target="_blank">https://localhost:3001/api/weather</A>&nbsp;rather than <A href="https://localhost/api/weather" target="_blank">https://localhost/api/weather.</A></P><P>To support this in our custom non-ExB apps we utilize <A href="https://webpack.js.org/configuration/dev-server/#devserverproxy" target="_blank">webpack-dev-server's proxy</A> configuration. It appears the ExB Dev Edition uses Koa to serve the application. It would be very helpful it ExB Dev Edition supported the configuration of a local proxy similar to webpack-dev-server's proxy. A quick search shows that Koa has a <A href="https://www.npmjs.com/package/koa-proxy" target="_blank">proxy middleware (koa-proxy)</A>&nbsp;that may be of use. Ideally, we could include a koa-proxy.js (or json) file to configure our proxy info.</P><P>This would make ExB Dev Edition more developer friendly; we would not need to code special logic for the dev only scenarios.</P> Tue, 15 Jul 2025 12:55:22 GMT RyanTaylor 2025-07-15T12:55:22Z https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idi-p/1633116 <P>During local development the experience is hosted on <A href="https://localhost:3001" target="_blank">https://localhost:3001</A> per the typical ExB installation and our backed API is hosted on <A href="https://localhost" target="_blank">https://localhost</A>&nbsp;(or another domain). However, the Integration, Acceptance, and Production frontend and backend deployments are all deployed on the <U>same domain</U>, e.g., <A href="https://mydomain.com/myapp" target="_blank">https://mydomain.com/myapp</A>.</P><P>When calling our custom backend API we use known relative paths — e.g.,&nbsp;fetch("api/weather") — as we prefer convention over configuration. However, this isn't workable as without a proxy the frontend sends requests to <A href="https://localhost:3001/api/weather" target="_blank">https://localhost:3001/api/weather</A>&nbsp;rather than <A href="https://localhost/api/weather" target="_blank">https://localhost/api/weather.</A></P><P>To support this in our custom non-ExB apps we utilize <A href="https://webpack.js.org/configuration/dev-server/#devserverproxy" target="_blank">webpack-dev-server's proxy</A> configuration. It appears the ExB Dev Edition uses Koa to serve the application. It would be very helpful it ExB Dev Edition supported the configuration of a local proxy similar to webpack-dev-server's proxy. A quick search shows that Koa has a <A href="https://www.npmjs.com/package/koa-proxy" target="_blank">proxy middleware (koa-proxy)</A>&nbsp;that may be of use. Ideally, we could include a koa-proxy.js (or json) file to configure our proxy info.</P><P>This would make ExB Dev Edition more developer friendly; we would not need to code special logic for the dev only scenarios.</P> Tue, 15 Jul 2025 12:55:22 GMT https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idi-p/1633116 RyanTaylor 2025-07-15T12:55:22Z https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idc-p/1634997#M4363 <P>1000%, this would help a lot with development!</P> Tue, 22 Jul 2025 15:15:28 GMT https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idc-p/1634997#M4363 NHannig 2025-07-22T15:15:28Z https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idc-p/1640830#M4433 <P>I greatly support this idea! The use of proxies was supported in WAB and it would be helpful to have it in the ExpBuilder too</P> Mon, 11 Aug 2025 12:12:20 GMT https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idc-p/1640830#M4433 LucVanDijk 2025-08-11T12:12:20Z https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idc-p/1674323#M4877 <P>I hope ESRI works on this</P> Fri, 19 Dec 2025 18:11:55 GMT https://community.esri.com/t5/arcgis-experience-builder-ideas/support-proxy-configuration-in-arcgis-experience/idc-p/1674323#M4877 NHannig 2025-12-19T18:11:55Z