Things like Cache-Control is also a client dependent config.. It may be set in the HTTP Server level, but these are not documented.. (at least not documented for Oracle.. I mean those .htaccess related tricks)
--> Header always set Cache-Control "no-cache, public" -- Note that; I didn't try that.. Probably this will not work..
Simillarly, for refferer-policy -> Header always set Referrer-Policy "same-origin"
Other than that, it is the client(The EBS Code that the client uses actually) that sets some meta to tell whether it wants the content to be cached or not.
There may be a config file for configuring the code ( making it set these types of meta according to the way we want), but I have no EBS to check that..
So you may check your EBS by recursively reading the configuration-related directory..(using the keywords Cache-Control and Referrer-Policy)
*These are packaged applications as you know. So you can't just do whatever you want before getting approval from Oracle. So you shouldn't change these types of things (undocumented and crucial) without getting Oracle's approval..
Anyways; create an Oracle SR and check the following in parallel;
Administering Security for Oracle HTTP Server, Configuring HTTP Secure Headers
https://docs.oracle.com/en/middleware/fusion-middleware/web-tier/12.2.1.4/secure-ohs/configuring-http-secure-headers.html