prerender

Vuetify + prerender-spa-plugin

走远了吗. 提交于 2020-05-30 08:42:08
问题 So I am using vuetify with "baseline" layout (from the documentation : https://vuetifyjs.com/en/examples/layouts/baseline). I set one page as pre rendered with : configureWebpack: { plugins: [ new PrerenderSPAPlugin({ // Required - The path to the webpack-outputted app to prerender. staticDir: path.join(__dirname, 'dist'), // Required - Routes to render. routes: [ '/about' ], }) ] } The page generated is fine. I made a compare with the html content from SPA and it's the same. However when the

how to test prefetch/prerender

放肆的年华 提交于 2020-01-23 04:48:09
问题 I have started to load a few key resources and pages using the prefetch/prerender system. Is there a way to ensure that the resources in question are actually being preloaded? 回答1: Google recommends using the Page Visibility API to test if a page is being prerendered. I'm not sure how well it works cross-browser (but what does in HTML5). 回答2: You can also use prerender-test.appspot.com to test that your site works correctly under prerendering. Further, from within Chrome, you can go to chrome

could not install prerender using npm - “Failed to locate: CL.exe”

℡╲_俬逩灬. 提交于 2020-01-10 08:40:34
问题 I've been trying to install PreRender.Io on my local machine to test. I've installed Python 2.7.10. When I type: npm install prerender It gives an error: C:\PreRender\node_modules\prerender\node_modules\phantom\node_modules\dnode\node _modules\weak>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\ node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild ) Building the projects in this solution one at a time. To enable

prerender basicAuth config

余生颓废 提交于 2020-01-03 17:25:33
问题 I'm running a prerender server and everything is okay but now I want to set some security using basicAuth. In my console, I have exported username an password export BASIC_AUTH_USERNAME=hugo export BASIC_AUTH_PASSWORD=boss In my server.js, I have added this line : server.use(prerender.basicAuth()); But the question is now, how do I configure my express server to call prerender with correct user/pass. I have this : var prerender = require('prerender-node').set('prerenderServiceUrl', 'http:/

prerender basicAuth config

大兔子大兔子 提交于 2020-01-03 17:25:21
问题 I'm running a prerender server and everything is okay but now I want to set some security using basicAuth. In my console, I have exported username an password export BASIC_AUTH_USERNAME=hugo export BASIC_AUTH_PASSWORD=boss In my server.js, I have added this line : server.use(prerender.basicAuth()); But the question is now, how do I configure my express server to call prerender with correct user/pass. I have this : var prerender = require('prerender-node').set('prerenderServiceUrl', 'http:/

Chrome Prerender feature gets canceled every time

雨燕双飞 提交于 2020-01-01 04:12:07
问题 I'm trying the prerender feature in chrome, but when I check the network, I can see the request is beeing canceled for any link. I'm using the following syntax: <link rel="prerender" href="http://example.org/index.html"> I tried the live demo at http://prerender-test.appspot.com/ and got the same result. Why is that? Update (from https://developers.google.com/chrome/whitepapers/prerender): In some cases while prerendering a site Chrome may run into a situation that could potentially lead to

Ember pre-render: timed out while initializing

狂风中的少年 提交于 2019-12-25 06:01:41
问题 I am trying to create a pre-render server for my ember app. I installed ember-prerender (https://github.com/zipfworks/ember-prerender), used the initializers provided in the /example, deployed it on one of my servers. But when I try to launch it: Restarting renderer, timed out while initializing This is the case even if I change engine (I tried with Phantom and jsdom). My best guess is that the XContentReady event is never fired. 回答1: So it was indeed XContentReady not firering that was

Extender controls may not be registered after PreRender. Occurs on GridView DataBind()

ぐ巨炮叔叔 提交于 2019-12-24 09:39:16
问题 On our ASP.Net 4.0 C# web app I get the error above in the subject line during debug. I'm not really doing anything funky with dynamic controls on the page as some search results indicated could have been the source of the problem. The page has 2 ajax:CalendarExtenders and has been working fine for a while. Although its probably related, I can see how really but this is what I was currently working on when the error came up. We have a control on the page that raises an event on an autorefresh

prerender.io IIS configuration

你说的曾经没有我的故事 提交于 2019-12-23 09:15:37
问题 I am trying to implement Prerender.io in my ASP.NET application. I configured all the required necessary steps including 1) <meta name="fragment" content="!"> in head of Index.html 2) Configured the Module <httpModules> <add name="Prerender" type="Prerender.io.PrerenderModule, IslamicMatchMakers.Web, Version=1.0.0.0, Culture=neutral" /> </httpModules> 3) Added Custom Header <httpProtocol> <customHeaders> <add name="X-Prerender-Token" value="XXXX" /> </customHeaders> </httpProtocol> 4) Defined

SEO with express.js and prerender-node

橙三吉。 提交于 2019-12-23 05:17:13
问题 Front-end: I have SPA client website that uses own routing system. For instance it has route http://localhost:8080/about Back-end: I'm using prerender-node on express.js server (runs on port 3001) to prerender static html for crawler bots: app.use(require('prerender-node') .set('prerenderServiceUrl', 'http://localhost:3000/') .set('afterRender', function (err, req, prerender_res) { console.log('URL: ', req.url); // here I see: "/about?_escaped_fragment_=" })); my express routing looks like