WAB with proxy 404 error

[JamesCrandall]

-WAB Developer 2.7

-.jsp proxy

-https

I have a WAB deployment that needs to authenticate secured feature services via proxy. Consider:

1. I am able to authenticate by clicking directly on a url with the proxy referenced as such:

https://domain.com/proxy/proxypage.jsp?https://domain.com/sitename/rest/services/foldername/feature_...

2. Opening the WAB gives a 404 error.

This is what's in the config.json:

"wabVersion": "2.7",
   "isTemplateApp": true,
   "isWebTier": false,
   "httpProxy": {
    "useProxy": true,
    "alwaysUseProxy": false,
    "url": "https://domain.com/proxy/proxypage.jsp",
    "rules": [
     {
      "urlPrefix": "https://domain.com/sitename/rest/services/foldername/feature_service_name/FeatureServer",
      "proxyUrl": "https://domain.com/proxy/proxypage.jsp"
     }
    ]
 },‍‍‍‍‍‍‍‍‍‍‍‍‍‍

[RobertScheitlin__GISP]

James,

   I would drop the FeatureServer portion of the url from your config.json rule.

[JamesCrandall]

Thank you! 

I made the suggested change in the config.json but still getting the 404 when attempting to access outside our network. 

1. The WAB opens fine when logged into corp network.

2. I can access the secured FS directly outside network with url specified in OP  This seems to suggest that the proxy.jsp page is correctly setup and there is another issue with the WAB somewhere?  The web map and wab are both shared to public from their AGOL items.

Thanks again.

[RobertScheitlin__GISP]

What is the actual url that is resulting in the 404 error?

[JamesCrandall]

sent as DM

[RandallWilliams]

This kinda sounds like a forward proxy issue instead of a proxy page issue. Unsure why the images are broken here:

How To: Set a proxy in the Web AppBuilder (Developer Edition) 

[JamesCrandall]

Thanks Randall -- we develop in WAB developer 2.7 with the node.js rather than command line (as suggested in the link).  However, the issue I'm having is with authenticating the deployed WAB itself. 

Thanks for this though as it'll likely fix the other issue when developing!

[JamesCrandall · Accepted solution]

This was an internal network problem and not related to the proxy page or WAB config.