diff options
author | 2016-09-14 15:01:16 -0700 | |
---|---|---|
committer | 2016-09-14 15:01:16 -0700 | |
commit | 1ed0b8e3d72abcc4788e89cab4caa4e8c0083985 (patch) | |
tree | 304e0cefda1020d57d878208b5614f0cc6d0670d /doc | |
parent | 83374d51662899adc08966ccca0d8d407f626df2 (diff) |
Add interop test for Cacheable Unary Calls
modified interop test spec doc
added CacheableUnaryCall to test.proto
modified server and client implmenentations to support new method
Diffstat (limited to 'doc')
-rw-r--r-- | doc/interop-test-descriptions.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/interop-test-descriptions.md b/doc/interop-test-descriptions.md index 1e04966380..5b3ad2335c 100644 --- a/doc/interop-test-descriptions.md +++ b/doc/interop-test-descriptions.md @@ -60,6 +60,27 @@ Client asserts: *It may be possible to use UnaryCall instead of EmptyCall, but it is harder to ensure that the proto serialized to zero bytes.* +### cacheable_unary + +This test verifies that gRPC requests marked as cacheable use GET verb instead +of POST, and that server sets appropriate cache control headers for the response +to be cached by a proxy. This interop test requires that the server is behind +a caching proxy. It is NOT expected to pass if client is accessing the server +directly. + +Server features: +* [CacheableUnaryCall][] + +Procedure: + 1. Client calls CacheableUnaryCall twice, and compares the two responses. + The server generates a unique response (timestamp) for each request. + If the second response was delivered from cache, then both responses will + be the same. + +Client asserts: +* call was successful +* responses are the same. + ### large_unary This test verifies unary calls succeed in sending messages, and touches on flow |