Developers can specifies the routing configuration of the app. The routing behavior is based on simple rules:
- The request path is matched against configured
- The longest matched prefix would be used.
- Path with
/_prefix is reserved for Skygear built-in APIs.
For example, in the following configuration:
- name: backend
- name: frontend
Requests would be routed to:
/_auth/login: Skygear Auth APIs
Requests with unmatched paths would be responded with status code 404.