Project

General

Profile

Actions

Bug #2217

closed

Varnish2+3 does not save custom VCLs vcl_fetch_early and vcl_fetch_late

Added by Magnus Forsberg about 12 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Varnish
Target version:
-
Start date:
02/20/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.0.1
Affected Plus Version:
Affected Architecture:
amd64

Description

Running pfSense 2.0.1-RELEASE.
Installed and tested Varnish and Varnish3

Varnish does save custom VCLs because of a typo in the custom XML.

/usr/local/pkg/varnish_custom_vcl.xml

How to fix:
diff b varnish_custom_vcl.xml varnish_custom_vcl.xml.org
118c118
< <fieldname>vcl_pipe_early</fieldname>
--

<fieldname>vcl_fetch_early</fieldname>

127c127
< <fieldname>vcl_pipe_late</fieldname>
---

<fieldname>vcl_fetch_late</fieldname>

Regards
/Magnus

Actions #1

Updated by Magnus Forsberg about 12 years ago

Sorry forgot pre..

diff -b varnish_custom_vcl.xml varnish_custom_vcl.xml.org
118c118
<                       <fieldname>vcl_pipe_early</fieldname>
---
>                       <fieldname>vcl_fetch_early</fieldname>
127c127
<                       <fieldname>vcl_pipe_late</fieldname>
---
>                       <fieldname>vcl_fetch_late</fieldname>

Actions #2

Updated by Scott Ullrich about 12 years ago

  • Status changed from New to Feedback

Please take a look at my commit. Next time please submit a diff -rub format as I can read that easier or do a pull request on Github using the edit file feature.

Thanks!

Actions #3

Updated by Magnus Forsberg about 12 years ago

Looks good :) I'll add another patch to vcl_deliver, submitting a feature patch.

Thanks!

Actions #4

Updated by Chris Buechler over 9 years ago

  • Category set to Varnish
  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF