Fix Apache reverse proxy paths and context alignment in BaSyx V2 example

[rheesk22mi]

Fix Apache reverse proxy configuration in BaSyx V2 example.

The original httpd.conf did not reflect the actual servlet context paths used by the BaSyx services, which caused 404 and proxy errors. This commit updates ProxyPass rules, adds trailing-slash redirects, and removes an invalid root proxy entry so that the example works as expected when deployed via docker-compose.

Pull Request Template

Description of Changes

This pull request fixes the Apache reverse proxy configuration in the BaSyx V2 example setup.

While following the example configuration provided in the repository, several endpoints were not reachable as documented. The main issue was a mismatch between the httpd.conf ProxyPass paths and the actual servlet context paths defined in docker-compose.yml.

The following adjustments were made:

• Updated ProxyPass routes to match the actual context paths (e.g., /aas-env instead of /aas-environment)
• Aligned the AAS Web UI proxy path with the configured BASE_PATH (/aas-ui)
• Added explicit trailing-slash redirects to prevent requests (e.g., /aas-env) from falling through to unintended proxy rules
• Disabled the root (/) ProxyPass pointing to a non-existing service, which previously caused 500 proxy errors due to DNS resolution failure

With these changes, all BaSyx components are accessible through the Apache reverse proxy as intended.

Related Issue

No existing issue was referenced.

This pull request addresses inconsistencies observed while setting up the Apache-based BaSyx V2 example.

BaSyx Configuration for Testing

The following setup was used for validation:

• Repository: basyx-java-server-sdk
• Docker Compose-based deployment
• Apache httpd:alpine container as reverse proxy
• BaSyx components:
  • AAS Environment (SERVER_SERVLET_CONTEXT_PATH=/aas-env)
  • AAS Registry (/aas-registry)
  • Submodel Registry (/sm-registry)
  • AAS Discovery Service (/aas-discovery)
  • AAS Web UI (BASE_PATH=/aas-ui)
    Apache was configured to listen on port 80 and proxy requests via path-based routing:
• http://localhost/aas-env/
  -http://localhost/aas-registry/
  -http://localhost/sm-registry/
  -http://localhost/aas-discovery/
  -http://localhost/aas-ui/
  All components were successfully accessed via the reverse proxy after applying the changes.

AAS Files Used for Testing

he default AAS files provided in the example (./examples/BaSyxReverseProxy/aasdirectory) were used for validation.
No additional AAS files were required to reproduce or verify the issue.

Additional Information

The issue was primarily caused by inconsistencies between:

• Documented example paths
• Servlet context paths defined in docker-compose.yml
• Apache ProxyPass configuration

Additionally, requests without trailing slashes (e.g., /aas-env) could fall through to the root proxy rule and cause DNS-related proxy errors. This has been mitigated by adding explicit redirect rules.

These changes improve stability and make the example setup work as expected when deployed using the provided Docker configuration.

[aaronzi]

Thanks for fixing the example. Seems like those mistakes were missed in the review.

Could you please sign the Eclipse Contributor Agreement with the same mail that you used to sign your commits. Otherwise I can't merge your PR.