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

Allow Caching of Nested Routes #11

Closed
srsgores opened this issue Jun 12, 2015 · 1 comment
Closed

Allow Caching of Nested Routes #11

srsgores opened this issue Jun 12, 2015 · 1 comment

Comments

@srsgores
Copy link

Currently, the implementation only works for the top-level / domain, but if you try to view a resource offline like /posts, since there's no posts/index.html cached, you will get the offline page.

I have tried editing the fallback section to serve index.html, but this still fails because the browser will request manifest.appcache from the nested domain, so resource/manifest.appcache. My next idea was to duplicate the top-level assets and files in the manifest.appcache, and this worked, but the problem was that this new appcache generated from the nested resource was overwriting the appcache initially created on the top-level (/).

Are there any suggestions on configuring nested resources/routes to work in a SPA application? Perhaps this isn't related to this particular plugin, but I thought it might be useful to explain that this plugin cannot deal with nested resources.

@ssured
Copy link
Contributor

ssured commented Aug 7, 2015

I use locationType: 'hash' in the Ember config, which solves the issue for me.

@ssured ssured closed this as completed Aug 7, 2015
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

No branches or pull requests

2 participants