We have a classic report on a page with which we are implementing a dynamic action to refresh on-the-fly when the user selects an option from a drop-down list. Our environment is that our production ApEx server is directly available to our internal staff, but only available to external, public users through a proxy pass server. External users use the URL of the proxy pass server, Apache on that server reroutes the traffic to our internal server, the internal server processes the request, then sends information back to the user.
When internal users access the page using the internal URL, the report works and refreshes perfectly as expected. When external users access the page via the proxy URL, the report doesn't show up at all and the proxy Apache error log file contains lines like these:
[Thu Sep 01 09:16:21 2011] [error] [client 172.16.20.15] File does not exist: /var/iris/f, referer: https://iris.ophth.wisc.edu/f?p=111:1506:878438001579004::NO:1506:P1506_DRAFT_SUBMISSION_RID:9342
[Thu Sep 01 09:25:19 2011] [error] [client 172.16.20.15] File does not exist: /var/iris/f, referer: https://iris.ophth.wisc.edu/f?p=111:1506:878438001579004::NO:1506:P1506_DRAFT_SUBMISSION_RID:9342
Also, while testing this in Firefox and Firebug, one of the console lines which display the dynamic action post, shows the following in the Results tab:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /f was not found on this server.</p>
<hr>
<address>Apache/2.2.16 (Ubuntu) Server at iris.ophth.wisc.edu Port 443</address>
</body></html>
My initial impression is that the built-in dynamic action programming is accessing the "f" function in a way that doesn't seem to be compatible with proxy pass server methods. But I have no way of proving or researching that theory. This phenomenon is only happening when users access the web page via the proxy server URL.
Any suggestions? Any details I left out that would be helpful?
Shane.
Additional Info: I just now tried refreshing the report using the new "$('#STATIC_ID_OF_REGION').trigger('apexrefresh');" syntax and that also did not work, producing the same results as described above.
Edited by: ShaneB on Sep 1, 2011 8:43 AM