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

MC-14863 Update Varnish version number #5047

Merged
merged 13 commits into from
Jul 30, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 14 additions & 10 deletions guides/v2.2/config-guide/varnish/config-varnish-install.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,26 +11,30 @@ functional_areas:

Installing the Varnish software is beyond the scope of this guide. For more information about installing Varnish, see:

* [installation wiki](http://wiki.mikejung.biz/Varnish)
* [Varnish installation guides](https://www.varnish-cache.org/docs)
* [How to install Varnish (Tecmint)](http://www.tecmint.com/install-varnish-cache-web-accelerator)
* [installation wiki](http://wiki.mikejung.biz/Varnish)
* [Varnish installation guides](https://www.varnish-cache.org/docs)
* [How to install Varnish (Tecmint)](http://www.tecmint.com/install-varnish-cache-web-accelerator)

{:.bs-callout .bs-callout-info}
This topic is written for Varnish on CentOS and Apache 2.2. If you're setting up Varnish in a different environment, some commands are likely different. Consult the preceding documentation for more information.<br><br>If you intend to install Varnish modules (vmods), such as saint mode, you should install Varnish by compiling the code, rather than installing from a package. See [Saint mode]({{ page.baseurl }}/config-guide/varnish/config-varnish-advanced.html#saint) for more details.
This topic is written for Varnish on CentOS and Apache 2.2. If you are setting up Varnish in a different environment, some commands are likely different. Consult the preceding documentation for more information.<br><br>If you intend to install Varnish modules (vmods), such as saint mode, you should install Varnish by compiling the code, rather than installing from a package. See [Saint mode]({{ page.baseurl }}/config-guide/varnish/config-varnish-advanced.html#saint) for more details.

## Confirm your Varnish version {#config-varnish-version}

Enter the following command to display the version of Varnish you're running:
Enter the following command to display the version of Varnish you are running:

varnishd -V
```bash
varnishd -V
```

A sample follows:

varnishd (varnish-4.0.3 revision b8c4a34)
Copyright (c) 2006 Verdens Gang AS
Copyright (c) 2006-2014 Varnish Software AS
```terminal
varnishd (varnish-4.0.3 revision b8c4a34)
Copyright (c) 2006 Verdens Gang AS
Copyright (c) 2006-2014 Varnish Software AS
```

Make sure the version is 4.x or 5.x before continuing. If you are running version 3.x, you must upgrade to a supported version. Consult the Varnish installation documentation for more information.
Make sure the version is 4.x, 5.2 or 6.x before continuing. If you are running version 3.x, you must upgrade to a supported version. Consult the Varnish installation documentation for more information.

### Next step

Expand Down
2 changes: 1 addition & 1 deletion guides/v2.3/graphql/caching.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Magento explicitly disallows caching the following queries.

We recommend setting up Varnish as a reverse proxy to serve the full page cache in a production environment. See [Configure and use Varnish]({{page.baseurl}}/config-guide/varnish/config-varnish.html) for more information.

Magento 2.3.2 updates the `vcl_hash` subroutine in the template `varnish.vcl` file and creates the `process_graphql_headers` subroutine for both Varnish 4.x and 5.x. To enable GraphQL caching, either generate a new template file, or edit the `default.vcl` file on your system to match the current default template.
As of Magento 2.3.2, Magento supports GraphQL caching with Varnish. If you have upgraded from a previous version, you can enable GraphQL caching by generating a new template file, or by editing the `default.vcl` file on your system to match the current default template for your version of Varnish.

If you choose to edit an existing `default.vcl` file, update the `vcl_hash` subroutine to check whether the request URL contains `graphql`, as follows:

Expand Down
2 changes: 1 addition & 1 deletion guides/v2.3/install-gde/system-requirements-tech.md
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ Mail Transfer Agent (MTA) or an SMTP server

* [Redis]({{page.baseurl}}/config-guide/redis/config-redis.html) versions 3.2, 4.0, 5.0 (compatible with 2.4+) for page caching and session storage.
Version 5.0 is highly recommended.
* [Varnish]({{page.baseurl}}/config-guide/varnish/config-varnish.html) version 4.x or 5.2
* [Varnish]({{page.baseurl}}/config-guide/varnish/config-varnish.html) version 4.x, 5.2 or 6.2
* [Elasticsearch]({{page.baseurl}}/config-guide/elasticsearch/es-overview.html)

{{site.data.var.ee}} version 2.3.x supports the following Elasticsearch versions:
Expand Down