Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvdp-pesi
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Jobs
Commits
Open sidebar
uplex-varnish
libvdp-pesi
Commits
3bb32079
Unverified
Commit
3bb32079
authored
Feb 24, 2023
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Adjust to range filter improvements in Varnish-Cache
Ref: 7da66c9b03f82b97e2476d5d0af62e58e0419216
parent
32532a98
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
8 deletions
+4
-8
e00015.vtc
src/tests/e00015.vtc
+4
-8
No files found.
src/tests/e00015.vtc
View file @
3bb32079
...
...
@@ -94,8 +94,6 @@ varnish v1 -syntax 4.1 -vcl+backend {
}
}
# Note on Range requests: The range VDP is active, but as it cannot
# reliably determine the size of the response, it falls back to a 200
client c1 {
txreq -url /top2
rxresp
...
...
@@ -111,11 +109,10 @@ client c1 {
expect resp.http.was == true
expect resp.http.filters == "pesi"
# see Note on Range above
txreq -url "/esi" -hdr "Range: bytes=1-2"
rxresp
expect resp.bodylen ==
76
expect resp.status == 20
0
expect resp.bodylen ==
2
expect resp.status == 20
6
expect resp.http.was == true
expect resp.http.filters == "pesi range"
...
...
@@ -126,11 +123,10 @@ client c1 {
expect resp.http.was == true
expect resp.http.filters == "pesi gunzip"
# see Note on Range above
txreq -url "/recurse" -hdr "Range: bytes=1-2"
rxresp
expect resp.bodylen ==
120
expect resp.status == 20
0
expect resp.bodylen ==
2
expect resp.status == 20
6
expect resp.http.was == true
expect resp.http.filters == "pesi gunzip range"
} -run
...
...
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