APEX

I am getting a 403 Forbidden browser error when calling a PL/SQL procedure from the URL, as in this:

http://<server.port>/apex/SCHEMA.procedure_name/f?p_param1=394&p_param2=2, etc


We are upgrading from HTMLDB 2.0 to APEX 4.0.2. I do not believe the upgrade has anything to do with it, c/o the upgraded app works fine in another APE 4.0.2 environment.

The upgrade is to new machines, new DB and new app server, Oracle Web Tier, Oracle HTTP server deployment.


The dads.conf entries are fine, all standard:

Alias /i/ "/apexd01/app/oracle/product/http/Oracle_WT1/ohs/images/"
Alias /c/ "/apexd01/app/oracle/product/http/Oracle_WT1/ohs/custom_htmldb/"

<Location /pls/apexd>
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlDatabaseConnectString dbserver.us.com:1521:SERVER.US.COM ServiceNameFormat
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword apexpwd
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
Allow from all
</Location>


The GRANT EXECUTE ON procedure TO PUBLIC is there.

A call to the same procedure via a process in an APEX page works fine - the procedure is OK.
The call from javascript, which sets up the call from the URL, is the one that fails with the 403 Forbidden error.

The same app works fine in another APEX 4.0.2 environment, so I know it is not the JS; It has to be some configuration setting in this environment.

I do NOT have access to the app server.
I have asked that they compare the httpd.conf, and all underlying conf files, to check for differences.

In order for me to be more specific, and hopefully speed up the troubleshooting process, can anyone suggest what other settings to look at?

Thank you - Karen