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

Do not cache empty responses #23

Merged
merged 1 commit into from
Feb 2, 2017
Merged

Do not cache empty responses #23

merged 1 commit into from
Feb 2, 2017

Conversation

pkittenis
Copy link
Collaborator

No description provided.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 94.272% when pulling d1e5c73 on negative_caching into 6bfa4c0 on master.

4 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 94.272% when pulling d1e5c73 on negative_caching into 6bfa4c0 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 94.272% when pulling d1e5c73 on negative_caching into 6bfa4c0 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 94.272% when pulling d1e5c73 on negative_caching into 6bfa4c0 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 94.272% when pulling d1e5c73 on negative_caching into 6bfa4c0 on master.

@pkittenis pkittenis merged commit e342bd7 into master Feb 2, 2017
@pkittenis pkittenis deleted the negative_caching branch February 2, 2017 17:34
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.

2 participants