-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Implement SSI sub-request strategy #9419
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
Comments
+1 |
Anyone willing to work on this one? It should be relatively easy by basing the work on the current ESI implementation. |
it would be great 🚤 /ping @kingcrunch |
I slightly remember, why I abanonded the PRs and build it up as separate bundle. The changes would introduce several BC-breaks (renaming interfaces at least, some different signatures, especially constructor ( I also wont promise to find time. It's a quite busy time for me right now. But I'd surely like to give it a second try (although I wouldn't be too sad, if somebody else would take it over 😉 ) |
👍 |
👍 |
This PR was merged into the 2.6-dev branch. Discussion ---------- [HttpKernel][FrameworkBundle] SSI support | Q | A | ------------- | --- | Bug fix? | No | New feature? | Yes | BC breaks? | No | Deprecations? | No | Tests pass? | Yes | Fixed tickets | #9419 (, #10684) | License | MIT It does not support comments, or alternative URIs, or "continue" in case of errors. Maybe I can workaround that, but I've decided to left it out for this PR. Especially as far as I can see a "alternative URIs"-hack would _always_ lead to two requests, even if it's not needed. Commits ------- 06cea08 SSI support
SSI support was planned for Symfony 2.3 as mentioned in the blog post http://symfony.com/blog/new-in-symfony-2-2-the-new-fragment-sub-framework.
Closed PRs: #6108, #6720, #6766
The text was updated successfully, but these errors were encountered: