Skip to content

Reviewed Cache cookbook articles #5096

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

Merged
merged 2 commits into from
Apr 15, 2015

Conversation

javiereguiluz
Copy link
Member

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

Although I admit that I don't use Varnish, I think the current documentation is a bit confusing. I haven't added or deleted any content, but I reordered things to make them easier to read and understand.


This port depends on your setup. Lets say that external connections come in
This port depends on your setup. Let's say that external connections come in
Copy link
Member

Choose a reason for hiding this comment

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

We don't use "we".

Copy link
Member Author

Choose a reason for hiding this comment

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

I've reworded it a bit, but I don't know if it's enough.

@xabbuh
Copy link
Member

xabbuh commented Mar 19, 2015

Sounds good to me. Maybe @dbu can also take a look at these changes.

connections, there is another proxy (as Varnish does not do HTTPS itself) on the
default HTTPS port 443 that handles the SSL termination and forwards the requests
as HTTP requests to Varnish with a ``X-Forwarded-Proto`` header. In this case,
add the following to your Varnish configuration:
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe we should first say that the terminator should set this header, and varnish will forward the headers to the application. that would be the right place for this. and only if the proxy in front of varnish can not be made to set the headers, one can hack them into varnish.

Copy link
Member

Choose a reason for hiding this comment

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

@dbu You're referring specifically to the X-Forwarded-Port, correct? In other words, the proxy that is terminating the SSL should set the X-Forwarded-Proto AND the X-Forwarded-Port headers. But in case X-Forwarded-Port is not set by that layer for some reason, you can add the below hack to Varnish so that it adds it.

Am I correct? Thx :)

Copy link
Contributor

Choose a reason for hiding this comment

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

@weaverryan yep, exactly, that is what i mean.

@weaverryan
Copy link
Member

Looks nice to me! I have one question out still to @dbu, and based on his response, I may make another small PR to tweak things. Thanks Javier!

@weaverryan weaverryan merged commit 80387cf into symfony:2.3 Apr 15, 2015
weaverryan added a commit that referenced this pull request Apr 15, 2015
This PR was merged into the 2.3 branch.

Discussion
----------

Reviewed Cache cookbook articles

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | all
| Fixed tickets | -

Although I admit that I don't use Varnish, I think the current documentation is a bit confusing. I haven't added or deleted any content, but I reordered things to make them easier to read and understand.

Commits
-------

80387cf Minor rewording
f11fe4f Reviewed Cache cookbook articles
@javiereguiluz javiereguiluz deleted the update_cache_cookbook branch January 3, 2018 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants