Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvfp-brotli
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
libvfp-brotli
Commits
de134c26
Commit
de134c26
authored
Feb 17, 2019
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add the ERRORS doc section.
parent
08663e71
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
36 additions
and
2 deletions
+36
-2
README.rst
README.rst
+18
-1
vfp_brotli.vcc
src/vfp_brotli.vcc
+18
-1
No files found.
README.rst
View file @
de134c26
...
...
@@ -460,7 +460,24 @@ log; to see it, set the ``varnishd`` parameter ``vsl_mask`` to
ERRORS
======
XXX ...
If errors are encountered during compression or decompression, they
are reported in the Varnish log with the tag ``FetchError`` (see
``vsl(7)``). The ``FetchError`` message for decompression errors
includes the error message from the brotli decoder library.
If the decoder reaches end-of-stream indicators, signaling a completed
decompression, but there are still additional bytes in the response
body, then the filter fails with the ``FetchError`` message "Junk
after brotli data".
The backend fetch fails when any VFP filter fails, which can lead to a
"503 Backend fetch failed" response from Varnish. When streaming is
enabled (i.e when the VCL variable ``beresp.do_stream`` variable is
``true``, which is the default), the error might not be detected until
after the response code and header have already been sent to the
client; then it is too late to change the response status. In such
cases, the client response body may be empty, and the network
connection to the client is closed.
REQUIREMENTS
============
...
...
src/vfp_brotli.vcc
View file @
de134c26
...
...
@@ -424,7 +424,24 @@ log; to see it, set the ``varnishd`` parameter ``vsl_mask`` to
ERRORS
======
XXX ...
If errors are encountered during compression or decompression, they
are reported in the Varnish log with the tag ``FetchError`` (see
``vsl(7)``). The ``FetchError`` message for decompression errors
includes the error message from the brotli decoder library.
If the decoder reaches end-of-stream indicators, signaling a completed
decompression, but there are still additional bytes in the response
body, then the filter fails with the ``FetchError`` message "Junk
after brotli data".
The backend fetch fails when any VFP filter fails, which can lead to a
"503 Backend fetch failed" response from Varnish. When streaming is
enabled (i.e when the VCL variable ``beresp.do_stream`` variable is
``true``, which is the default), the error might not be detected until
after the response code and header have already been sent to the
client; then it is too late to change the response status. In such
cases, the client response body may be empty, and the network
connection to the client is closed.
REQUIREMENTS
============
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment