JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.2p0 | CONFIDENTIAL | CodeSecure Inc |
Some reverse proxy behaviors can interfere with communication between the CodeSonar analysis and the hub.
This task describes how to configure your reverse proxy to allow CodeSonar to work correctly, using NGINX as an example.
Note that it is not possible to use certificate-based hub authentication in the presence of a proxy or reverse proxy.
Reverse proxy behaviors such as buffering, caching, and timeouts can interfere with communication between the CodeSonar analysis and the hub.
Configuring your reverse proxy to allow CodeSonar to work correctly will generally include the following.
Note: It is not possible to use certificate-based hub authentication in the presence of a proxy or reverse proxy. TLS client authentication is designed to prevent "man in the middle" attacks and the reverse proxy is a man in the middle.
The following NGINX configuration will allow CodeSonar to work correctly.
http {
server {
...
...
location / {
...
...
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_buffering off;
proxy_cache off;
proxy_request_buffering off;
proxy_read_timeout 1w;
proxy_connect_timeout 300s;
}
}
}
For more information about these settings, see the following links.
To report problems with this documentation, please visit https://support.codesecure.com/.