Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[now dev] Add etag response header for Lambda invocations #2502

Merged
merged 1 commit into from Jul 7, 2019

Conversation

TooTallNate
Copy link
Member

This matches the behavior in production.

This matches the behavior in production.
@TooTallNate TooTallNate requested a review from leo as a code owner July 6, 2019 02:33
@codecov-io
Copy link

Codecov Report

Merging #2502 into canary will increase coverage by 0.06%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           canary    #2502      +/-   ##
==========================================
+ Coverage   11.37%   11.43%   +0.06%     
==========================================
  Files         256      257       +1     
  Lines        9247     9250       +3     
  Branches     1031     1030       -1     
==========================================
+ Hits         1052     1058       +6     
+ Misses       8083     8080       -3     
  Partials      112      112
Impacted Files Coverage Δ
src/util/dev/types.ts 0% <ø> (ø) ⬆️
src/util/dev/server.ts 47.37% <ø> (+0.11%) ⬆️
src/util/dev/builder-cache.ts 67.88% <100%> (-0.87%) ⬇️
src/util/dev/builder.ts 67.66% <100%> (+0.39%) ⬆️
src/util/sha.ts 100% <100%> (ø)
src/util/metrics.ts 68.18% <0%> (+6.64%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2414767...30db13e. Read the comment docs.

@leo leo merged commit f80f1f7 into canary Jul 7, 2019
@leo leo deleted the update/now-dev-add-etag-for-lambdas branch July 7, 2019 13:19
leo pushed a commit that referenced this pull request Jul 7, 2019
This matches the behavior in production.
TooTallNate added a commit that referenced this pull request Jul 9, 2019
This reverts commit f80f1f7 (#2502).

`ETag` header is only sent in production when the lambda function sets
the "stale-while-revalidate" cache-control header, which will be
implemented in a separate PR.
TooTallNate added a commit that referenced this pull request Jul 9, 2019
…2520)

* [now dev] Revert "Add `etag` response header for Lambda invocations"

This reverts commit f80f1f7 (#2502).

`ETag` header is only sent in production when the lambda function sets
the "stale-while-revalidate" cache-control header, which will be
implemented in a separate PR.

* Remove `etag` test assertion
AndyBitz pushed a commit that referenced this pull request Jul 12, 2019
…2520)

* [now dev] Revert "Add `etag` response header for Lambda invocations"

This reverts commit f80f1f7 (#2502).

`ETag` header is only sent in production when the lambda function sets
the "stale-while-revalidate" cache-control header, which will be
implemented in a separate PR.

* Remove `etag` test assertion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants