🚀 Feature: Support path-based routing #75

New Issue

AtHeartEngineer · 2025-07-08T08:39:05-04:00

AtHeartEngineer commented

2025-07-08 08:39:05 -04:00

Originally created by @jcstryker on 6/10/2025

Feature description

Followup to https://github.com/pocket-id/pocket-id/issues/224

I am suggesting enabling support for hosting the pocket-id web app on a path other than /, e.g. https://foo.bar/auth or https://foo.bar/id

Pitch

This would enable deploying the app in environments without DNS e.g. virtual machines or docker images that only are accessible via IP - requiring apps to be routed based on path instead of subdomain.

There are other benefits to path-based routing that make it preferable in certain production environments including:

Sub-domain routing is controlled by the DNS system and therefore can be routed without requiring any input from the server hosting the site. Changes to routing have a time-lag and traffic can be manipulated if DNS is compromised in a way that is harder to detect than on a single domain.
Path-based routing is controlled by the web server and can be applied instantaneously, maintaining a tight ownership boundary for the application
Path-based routing can simplify regex matching and filtering for many reverse proxy implementations, especially those used in the Kubernetes ecosystem and enterprise use cases.

*Originally created by @jcstryker on 6/10/2025* ### Feature description Followup to https://github.com/pocket-id/pocket-id/issues/224 I am suggesting enabling support for hosting the pocket-id web app on a path other than `/`, e.g. `https://foo.bar/auth` or `https://foo.bar/id` ### Pitch This would enable deploying the app in environments without DNS e.g. virtual machines or docker images that only are accessible via IP - requiring apps to be routed based on path instead of subdomain. There are other benefits to path-based routing that make it preferable in certain production environments including: - Sub-domain routing is controlled by the DNS system and therefore can be routed without requiring any input from the server hosting the site. Changes to routing have a time-lag and traffic can be manipulated if DNS is compromised in a way that is harder to detect than on a single domain. - Path-based routing is controlled by the web server and can be applied instantaneously, maintaining a tight ownership boundary for the application - Path-based routing can simplify regex matching and filtering for many reverse proxy implementations, especially those used in the Kubernetes ecosystem and enterprise use cases.

AtHeartEngineer closed this issue

2025-07-08 08:39:05 -04:00

AtHeartEngineer added the feature feature feature feature feature feature feature feature feature feature labels 2025-07-08 08:39:07 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pocket-id#75