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
d8bc0938
Commit
d8bc0938
authored
Aug 01, 2019
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add HTTP/2 tests to pesi.vtc (currently with intermittent errors).
parent
445cfc63
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
70 additions
and
0 deletions
+70
-0
pesi.vtc
src/tests/pesi.vtc
+70
-0
No files found.
src/tests/pesi.vtc
View file @
d8bc0938
...
...
@@ -43,3 +43,73 @@ client c1 {
rxresp
expect resp.body == "DATA"
} -run
## HTTP/2
varnish v1 -stop
barrier b2 cond 2
server s2 {
rxreq
txresp -body {<esi:include src="someurl"/>}
} -start
server s3 {
rxreq
txresp -body {<esi:include src="otherurl"/>}
} -start
server s4 {
rxreq
barrier b2 sync
delay 1
txresp -body {DATA}
} -start
varnish v2 -arg "-p debug=+waitinglist -p feature=+http2" -vcl+backend {
import ${vmod_pesi};
sub vcl_backend_fetch {
if (bereq.url == "/") {
set bereq.backend = s2;
}
elsif (bereq.url == "someurl") {
set bereq.backend = s3;
}
else {
set bereq.backend = s4;
}
}
sub vcl_backend_response {
set beresp.do_esi = true;
}
sub vcl_deliver {
pesi.activate();
}
} -start
client c1 -connect "${v2_sock}" {
stream 1 {
txreq
rxresp
expect resp.status == 200
expect resp.body == "DATA"
} -start
stream 3 {
txreq
barrier b2 sync
rxresp
expect resp.status == 200
expect resp.body == "DATA"
} -run
stream 5 {
txreq
rxresp
expect resp.status == 200
expect resp.body == "DATA"
} -run
stream 1 -wait
} -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