8000 document the mysterious abc part of the header by greg0ire · Pull Request #3880 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

document the mysterious abc part of the header #3880

8000
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

Closed
wants to merge 1 commit into from

Conversation

greg0ire
Copy link
Contributor

One can't help but wonder what it is about. Disclaimer: I'm far from being a specialist, I barely know varnish. This is what I understand after a cursory reading of this document. Please check this carefully.

Q A
Doc fix? yes
New docs? yes
Applies to all
Fixed tickets none

several surrogates are being chained. This way, your application is able to
target individual devices with specific directives. Just make sure each token
is unique.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should turn this into a note, and mostly link to the docs on this, as I think most users won't need to worry about this (but I like the idea of showing people where they can find out more, I didn't know what the abc was before this either).:

.. note::

    The ``abc`` part of the header isn't important unless you have multiple "surrogates"
    that need to advertise their capabilities. See `Surrogate-Capability Header`_ for details.

Then at the bottom of the page:

.. _`Surrogate-Capability Header`: http://www.w3.org/TR/edge-arch

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I'll change this later.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done and rebased on master (I made the PR on master, not sure why, tell me if you would like me to close it and make another on 2.3)

One can't help but wonder what it is about.
@weaverryan
Copy link
Member

👍 Great addition - thanks Grégoire!

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

Successfully merging this pull request may close these issues.

2 participants
0