Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite rules and headers #27

Open
brendt opened this issue Oct 21, 2017 · 1 comment
Open

Rewrite rules and headers #27

brendt opened this issue Oct 21, 2017 · 1 comment
Assignees
Labels

Comments

@brendt
Copy link
Collaborator

brendt commented Oct 21, 2017

At this moment, Stitcher heavily relies on .htaccess to handle URL rewrites and setting custom headers, for eg. HTTP/2 server push support.

It's well known that .htaccess has a performance cost, and is better avoided. Furthermore by relying on .htaccess, Stitcher won't work out of the box on nginx servers.

It would be better to let Stitcher handle routing itself. This means a PHP script has to run on every request, but it offers a lot more flexibility:

  • Handle routing and headers without being dependent on the underlying webserver.
  • It's much more easy to add dynamic extensions to a static website.

So the question is: which router to use, and how to handle the mapping of headers for each route (they should still be generated during compiletime, not runtime).

@brendt brendt added the v2 label Oct 21, 2017
@brendt brendt self-assigned this Oct 21, 2017
@brendt brendt mentioned this issue Oct 21, 2017
@brendt
Copy link
Collaborator Author

brendt commented Oct 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant