Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How do I assert a different hostname, port, or request_protocol to the PL/SQL application?

0
Posted

How do I assert a different hostname, port, or request_protocol to the PL/SQL application?

0

In situations where your OHS instance is front-ended by Web Cache or a Load Balancing Router, there is a need to assert the hostname and port for the site to be that of the Web Cache or the LBR. In such situations, it is recommended that you use the OHS configuration directives ServerName and Port to do the assertion. If for some reason, you do not wish to assert the hostname and port at the OHS level, you can use the mod_plsql configuration directive PlsqlCGIEnvironmentList to assert a different hostname and port to only the PL/SQL applications running under mod_plsql. For example: PlsqlCGIEnvironmentList SERVER_NAME=lbr.us.oracle.com Consider using OHS’ ServerName directive in httpd.conf instead. PlsqlCGIEnvironmentList SERVER_PORT=9999 Consider using OHS’ Port directive in httpd.conf instead. PlsqlCGIEnvironmentList HTTP_HOST=myservername.us.oracle.com:9999 Combination of SERVER_NAME:SERVER_PORT. Similarly, in cases where your site is accessed externally as an SSL, but is internally

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123