What to add for context paths
If your application uses context paths, then you will need to provide us a list of the context paths. This is so that we can map the Domain to the APIs we find in your codebase.
Webserver
If you are using a webserver to add context paths (Nginx / HAProxy / Traefik / Istio) you will have a configuration file that you can download and paste below.
Nginx
/etc/nginx/nginx.conf
/etc/nginx/sites-available/default
/etc/nginx/sites-available
Specifically we care about anything that looks like the following:
Apache HTTP Server
Configuration Files:
/etc/httpd/conf/httpd.conf
Any
.conf
in/etc/httpd/conf.d
Example:
Tomcat
Configuration Files:
/conf/server.xml
or any.xml
places inconf/Catalina/localhost
for each application
Example:
Jetty
Configuration Files:
This can be a wide variety of configuration files (there is no single place for Jetty to define this). Look for xml configuration files.
Example:
HAProxy
Configuration Files:
Typically found at
/etc/haproxy/haproxy.cfg
Example:
Cloud Service
If you are using a cloud service to add context paths (AWS ALB, Azure Application Gateway, AWS API Gateway etc), you will have to go their respective configurations and pull out the context paths.
AWS API Gateway
Azure Application Gateway
Azure Front Door