Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Adjust the Varnish HTTP response size #1225

Merged
merged 5 commits into from
Jun 19, 2017
Merged

Adjust the Varnish HTTP response size #1225

merged 5 commits into from
Jun 19, 2017

Conversation

jeff-matthews
Copy link
Contributor

No description provided.

@jeff-matthews jeff-matthews requested a review from keharper June 19, 2017 13:17
@jeff-matthews jeff-matthews changed the title Jm 1202 adjust http resp size Adjust the Varnish HTTP response size Jun 19, 2017
To resolve this issue, increase the default value of `http_resp_hdr_len` in your Varnish configuration file as follows:
To resolve this issue, increase the default value of the `http_resp_hdr_len` parameter in your Varnish configuration file. The `http_resp_hdr_len` parameter specifies the max header length _within_ the total default response size (32K).

<div class="bs-callout bs-callout-info" id="info">
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI. You don't have to change this. Use this to define your Note block:

<div class="bs-callout bs-callout-info" id="info" markdown="1">

As a result, you don't need the span, p, and code elements (though you'd still need to use the backticks for the parameter)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for letting me know. I copy/pasted the original from elsewhere, but I prefer the simplicity of your recommended syntax.

@jeff-matthews jeff-matthews merged commit 229c0a0 into magento:develop Jun 19, 2017
@jeff-matthews jeff-matthews deleted the jm_1202_adjust_http_resp_size branch June 19, 2017 15:50
magento-cicd2 pushed a commit that referenced this pull request Sep 21, 2017
Regenerated backward incompatible changes between develop and 2.1.9
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants