Skip to content

Remove custom Guzzle client docs from feature #138

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 1 commit into from
Aug 14, 2014
Merged

Conversation

ddeboer
Copy link
Member

@ddeboer ddeboer commented Aug 14, 2014

The information seems too detailed to be shown in Features, so have it in
Configuration only instead.

The information seems too detailed to be shown in Features, so have it
in Configuration only instead.
ddeboer added a commit that referenced this pull request Aug 14, 2014
Remove custom Guzzle client docs from feature
@ddeboer ddeboer merged commit 182c05d into master Aug 14, 2014
@ddeboer ddeboer deleted the custom-guzzle-docs branch August 14, 2014 08:00
with the caching proxy. If you need to customize the requests, for example to
send a basic authentication header, you can inject a custom Guzzle client::
See the
:doc:`/reference/configuration/proxy-client#custom-guzzle-client` configuration reference.
Copy link
Contributor

Choose a reason for hiding this comment

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

i would have kept a .. tip:: here saying that if you need some headers on every request you should do a custom guzzle and link (with a :ref:, not the :doc: link). people reading here will just see "ah i can send some header, so lets just hardcode (or inject) that header everywhere i use the proxy client or cache manager"

Copy link
Member Author

Choose a reason for hiding this comment

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

Done in 71fff50.

Copy link
Contributor

Choose a reason for hiding this comment

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

thanks

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.

3 participants