Nice to know, check what events are happening on the webpage…
start Chrome
open the website
F12 for developer tools
open the console (ESC) and type:
monitorEvents(document.body)hit enter, return to your webpage and observe the console
be amazed
Have a nice day!
Again, found and pasted here; to keep for myself and later use.
Article from March 2018, but still valid I think. Original link: https://www.seoguru.nl/handleiding-seo/seo-tips/ = the last chapter of https://www.seoguru.nl/handleiding-seo/
Tot slot van deze handleiding geef ik hier een samenvatting in de vorm van SEO tips. Ze zijn hieronder zoveel mogelijk uitgesorteerd naar het stadium van de ontwikkeling van de website. De lijst wordt regelmatig bijgehouden. Indien u zaken ziet die naar uw mening anders moeten of indien u tips mist, dan hoor ik dat graag. Dank!
Continue reading SEO tips from the guruPrevent caching?
change the HEADERS!
Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache Expires: 0
GOOD INFO HERE:
https://stackoverflow.com/questions/49547/how-to-control-web-page-caching-across-all-browsers
Just correct this using CSS.
The appearance property is used to display an element using a platform-native styling based on the users’ operating system’s theme.
.thing {
-webkit-appearance: none;
-moz-appearance: none;
appearance: none;
}
Ja, http://blog.mybrain.nl/ is verhuisd naar https://markohoven.com/
Hoe doe je dit nu op een correcte manier?
Binnen IIS kan dit met web.config
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<httpRedirect enabled="true" destination="https://markohoven.com" httpResponseStatus="Permanent" />
<defaultDocument enabled="true">
<files>
<clear />
<add value="index.php" />
<add value="index.htm" />
<add value="index.html" />
<add value="default.asp" />
<add value="default.aspx" />
<add value="default.htm" />
<add value="default.html" />
</files>
</defaultDocument>
<httpErrors errorMode="Custom">
<remove statusCode="404" subStatusCode="-1" />
<error statusCode="404" prefixLanguageFilePath="" path="/index.php" responseMode="ExecuteURL" />
</httpErrors>
</system.webServer>
</configuration>
Een andere mogelijkheid is in code… Continue reading 301-redirect
… does not exist
https://nl.wikipedia.org/wiki/Lijst_van_HTTP-statuscodes
However it did take some of my time to figure this one out as the response code was really in my webserver logfiles and as usual… I was not the first to run into this problem, see: https://stackoverflow.com/questions/46266553/why-laravel-api-return-419-status-code-on-post-and-put-method
You get a 419 status code, if an (external) script tries to post to your Laravel application, without the o-so-needed CSRF token.
First option is to change in App\Http\Middleware\VerifyCsrfToken:
protected $except = [ ‘/*’, ];
(or maybe something more specific and a little more safe, like ‘/myapiurl/*’,)
Second option is to put the route in api.php instead of web.php, but that implies prefixing all your routes with /api/
… your choice!