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

apollo-cache-control does not set HTTP headers #2880

Closed
wants to merge 1 commit into from

Conversation

blimmer
Copy link

@blimmer blimmer commented Jun 18, 2019

I lost quite a bit of time to this and the tests finally showed me that enabling apollo-cache-control stops HTTP headers from being set.

it('contains no cacheControl Headers and keeps extension with engine proxy', async () => {
const { url: uri } = await createServer({
typeDefs,
resolvers,
cacheControl: true,
});
const apolloFetch = createApolloFetch({ uri }).useAfter(
(response, next) => {
expect(response.response.headers.get('cache-control')).toBeNull();
next();
},
);

This warning might help future folks.

Is this the expected behavior in all integrations? Or is this an oddity with apollo-server-express?

I lost quite a bit of time to this and the tests finally showed me that enabling apollo-cache-control stops HTTP headers from being set. This warning might help future folks.
@apollo-cla
Copy link

@blimmer: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

@abernix
Copy link
Member

abernix commented Jun 25, 2019

This sounds like a bug, not a documentation problem. I appreciate you opening the issue, but if you have some time (and since you have a working reproduction, it seems!) do you mind looking into the source of the bug? Perhaps it's related to recent changes, such as #2715, but maybe trying some older versions would help confirm?

If you're not able to look into it, opening an issue would be great, but I certainly don't want us to solidify this into the documentation as the expected norm and not look back.

Thanks!

@blimmer
Copy link
Author

blimmer commented Jun 25, 2019

No problem - I opened #2918

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants