add cache behavior modifiers to RequestInit interface

[trjstewart]

Documentation for these features can be found here , under the Overriding TTL and Override based on origin response code headings.

// Force response to be cached for 300 seconds.
fetch(event.request, { cf: { cacheTtl: 300 } })

// Force response to be cached for 86400 seconds for 200 status codes, 1 second for 404, and do not cache 500 errors
fetch(request, { cf: { cacheTtlByStatus: { '200-299': 86400, '404': 1, '500-599': 0 } } })

[jrf0110]

I think it'd be a good idea and add some comments on how to use this DSL. Show an @example of the range syntax

[trjstewart]

There are examples in the provided Cloudflare documentation. Or do you mean add examples to the readme?

[trjstewart]

@jrf0110 just bumping for some clarification please.

[ispivey]

I think he meant examples inline in the comments, like some of the other fields have. While it’s duplicative of the docs, this will ensure IDEs provide helpful documentation directly in your editor. We’d also like to auto-generate docs from these comments eventually.

Also, I recently merged a refactor that creates a conflict. You’ll want to put these on the new CfRequestInit interface, now, if you can rebase on master.

If you think you can update that sometime today or tomorrow, let us know — I’d love to include this in a 1.0.10 release on Friday.

Also happy to do that ourselves if you don’t have time!

[trjstewart]

@ispivey I should have time to do it today, if it's not done in the next 12 hours feel free to do so yourself if you have the time. Thanks heaps for the comment!

[trjstewart]

@ispivey I've added those examples if you're happy with that.

[ispivey]

Thanks, and thanks so much for contributing!