Oxaa
Sign inDownload
  1. Localhost. Online. Without opening your network.
  2. Documentation home
  3. CLI reference
  4. CLI: publish an HTTP service

Secure public endpoints for local development

CLI: publish an HTTP service

CLI: publish an HTTP service: practical workflow, product behavior, limits, evidence and the exact next step with Oxaa.

Fast answer

CLI: publish an HTTP service is an execution page, not a marketing summary. It states the supported scope, prerequisites, exact states, expected result, failure paths, cleanup and the next technical task.

From local service to a real external request

  1. Install the approved signed Oxaa package and verify the release.
  2. Run oxaa login and enroll the device.
  3. Start and health-check the selected local service.
  4. Run oxaa http <port> and wait for edge readiness.
  5. Send a request from a provider sandbox, remote browser, phone or second network.
  6. Confirm the request and response in the local application and Inspector.
  7. Stop the route and remove callbacks, captures and test credentials when finished.

Commands used on this page

oxaa http 3000

Technical details

  • target validation
  • local HTTP or explicit HTTPS upstream
  • connecting versus edge-ready
  • public URL and Inspector address
  • graceful stop and route cleanup
  • representative external request

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.