Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
a50b1d72
Commit
a50b1d72
authored
Jan 16, 2023
by
Dridi Boukelmoune
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
vtc: Polish r1506
Opportunity noticed during the review of #3872.
parent
9ec14234
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
6 deletions
+2
-6
r01506.vtc
bin/varnishtest/tests/r01506.vtc
+2
-6
No files found.
bin/varnishtest/tests/r01506.vtc
View file @
a50b1d72
...
...
@@ -2,7 +2,7 @@ varnishtest "range requests on streamed response"
barrier b1 cond 2 -cyclic
server s
1 -repeat 5
{
server s
0
{
rxreq
txresp -nolen \
-hdr "Transfer-Encoding: chunked" \
...
...
@@ -18,7 +18,7 @@ server s1 -repeat 5 {
send "11\r\n7_23456789abcdef\n"
chunkedlen 0
} -
start
} -
dispatch
varnish v1 -vcl+backend {} -start
...
...
@@ -31,7 +31,6 @@ client c1 {
barrier b1 sync
rxrespbody
expect resp.bodylen == 85
delay .1
# We cannot do tail-ranges when streaming
txreq -url /2 -hdr "Range: bytes=-10"
...
...
@@ -41,7 +40,6 @@ client c1 {
barrier b1 sync
rxrespbody
expect resp.bodylen == 136
delay .1
# We cannot do open-ranges when streaming
txreq -url /3 -hdr "Range: bytes=17-"
...
...
@@ -51,7 +49,6 @@ client c1 {
barrier b1 sync
rxrespbody
expect resp.bodylen == 136
delay .1
# Handles out of bounds range
txreq -url /4 -hdr "Range: bytes=102-200"
...
...
@@ -60,7 +57,6 @@ client c1 {
barrier b1 sync
rxrespbody
expect resp.bodylen == 34
delay .1
# Keeps working after short response
txreq -url /5 -hdr "Range: bytes=17-101"
...
...
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