Has anyone gotten data-ignore-cache to work?

Questions
1

I am trying to force a page to load from the server on each request. It appears to be cached and I cannot seem to make the ignore cache feature to work. I’m going back and forth between page 1 and page 2. Is this a known bug? Has anyone gotten this feature to work?

Live Demo

<!DOCTYPE html>
<html>
<body>
<div id="app">
	<div class="view view-main view-init">
		<div class="page">
			<div class="page-content">
				<a href="/admin/framework7/temp/2/" data-ignore-cache="true">Go to page 2</a>
			</div>
		</div>
	</div>
</div>

<script src="/admin/framework7/js/framework7.bundle.min.js"></script>
<script src="/admin/framework7/temp/routes.js"></script>
<script src="/admin/framework7/temp/app.js"></script>

</body>
</html>

Here is my page 2.asp

<template>
	<div class="page">
		<div class="page-content">
			This is page 2.  Time is <%= Now %>
			<br><br>
			<a href="#" class="back">Go back to page 1</a>
		</div>
	</div>
</template> <script>page 2 script code goes here</script>

Here is my app.js

// Dom7
var $$ = Dom7;

// Framework7 App main instance
var app  = new Framework7({
	root: '#app',					// App root element
	id: 'io.framework7.testapp',	// App bundle ID
	name: 'Framework7',				// App name
	theme: 'auto',					// Automatic theme detection
	routes: routes,
	view: {
		xhrCache: false
	}
});

Here is my routes.js

routes = [ 
	{
		path: '/admin/framework7/temp/2/',
		componentUrl: '/admin/framework7/temp/2.asp'
	}
];
2

Because you use componentUrl. Components are hard cached. There is no sense to return everytime different component. Component is component, it has template where you can and should specify required rendering conditions based on data

3

Thanks for the reply.

Maybe to you it makes no sense but how would I accomplish what I want to do?

Lets say I want to have 100 pages each with their own style and script tags. And every time a user goes to those pages I want them to NOT be cached. The only way I can see to separate script tags out of routes.js is to use componentUrl.

If I don’t separate the scripts to each page then my routes.js page is 1000’s of lines long. My users may not visit all 100 pages of my site so having a huge routes.js file makes no sense to me.

Maybe having a huge routes.js file is the only way to accomplish it. Wish you made an option to NOT cache componentUrls. Give your users the option. Don’t just assume they will never need to do it. Thanks!