Expose how cache key is computed

[kodermax]

Like this kodermax@21af4bd

[Kikobeats]

Hum, that doesn't mean mobile is not supported right now 🙂

In your fork, you need to check CloudFront-Is-Mobile-Viewer and that could be different in every use case.

For example, if you have a totally independent mobile site (like m.site.com) it means the site is totally different from the non-mobile, so it's supported by default.

Another example: Just using a query parameter for differentiating it in the cache storage should be enough (like mobile=iphone).

But I'm happy to support extend the default behavior, the most obvious next step could be possible to override .getKey, then you can put your custom logic here.

Thoughts?

[fabienheureux]

@Kikobeats this could be a great idea/solution. I ended up to stop using cacheable-response because of lack of this feature (and lack of time to find a workaround).