Oxaa
Sign inDownload
  1. Localhost. Online. Without opening your network.
  2. Framework and runtime guides hub
  3. Spring Boot expose-localhost guide

Secure public endpoints for local development

Spring Boot expose-localhost guide

Expose a local Spring Boot app through a managed HTTPS endpoint, test the stack-specific proxy behavior and receive a real external request.

Fast answer

Run a tested Spring Boot fixture locally, publish only its selected port and prove a real external request. This page must solve stack-specific behavior-forward-headers-strategy, context path, WebSocket/SSE and actuator exposure-rather than repeat the generic quickstart.

Step-by-step

  1. Use the supported Spring Boot and Oxaa versions and open the pinned example commit.
  2. Start the application with ./mvnw spring-boot:run or the repository’s documented development command.
  3. Verify a deterministic local health route on loopback.
  4. Run oxaa login and oxaa http <port>; wait for edge readiness.
  5. Open the public URL from a second network or provider sandbox.
  6. Test the stack-specific Host, proxy, cookie, redirect, raw-body and realtime behavior that applies.
  7. Confirm the expected local log, response and Inspector state.
  8. Stop the route, remove temporary configuration and archive the tested version.

Spring Boot-specific caveats

  • forward-headers-strategy
  • context path
  • WebSocket/SSE
  • actuator exposure

How traffic and Inspector data are handled

Oxaa's public edge terminates public HTTPS so it can resolve the exact hostname, identify the current authenticated route and forward the request. The session between the enrolled device and Oxaa is encrypted; the selected local service receives the request through that session.

Oxaa retains bounded account, route, usage, security, billing, support and diagnostic metadata required to operate and protect the service. Inspector body capture is a separate, explicit debugging action: the bounded request or response body copy shown by the local Inspector remains on the developer device and can be redacted, deleted or allowed to expire. Public traffic still has to be processed by the edge, so the accurate claim is local Inspector copies-not “Oxaa cannot see traffic.”

Troubleshooting

Start with the local process, port and scheme. Then check authentication and clock, DNS, UDP/443, TCP/443 fallback, corporate proxy or TLS interception, route ownership and edge readiness. Use oxaa routes list, oxaa diagnose --network and stable error IDs; review diagnostic output before sharing it and remove secrets, bodies and private paths.

Cleanup and production handoff

Remove the external callback, preview URL or DNS binding; rotate test credentials; delete local captures; stop the route; and revoke the device or session when appropriate. Move production traffic to the deployed application, production ingress or event-delivery platform designed for that job.

What Oxaa is - and is not

Oxaa is development connectivity for a selected local HTTP or HTTPS service while the enrolled device and authenticated route are live. It is not application hosting, a general VPN, a forward proxy, permanent production deployment, raw TCP/UDP tunneling, arbitrary TLS passthrough, a CDN/WAF replacement or a production webhook delivery platform.