Vulnerability in EPiServer.Forms
We're preparing to launch our first EPiServer site soon and so are looking at how we can redirect links from the old site to our new site.
For some of the old URLs they will map exactly to the enw ones so no worries, but for those that will be redirected there is a chance that the URL could exist in its own right with the CMS at a later date.
Does anyone have an approach to managing this that allows EPiServer to have a go at handling the URL before falling back to some hardcoded redirect rules? Or even better does anyway have an approach to allow these to be managed within the CMS (without shelling out more money, so no SEO Manager).
We usually use the 404Handler module for this. https://www.coderesort.com/p/epicode/wiki/404Handler. Also available through EPiServer's NuGet feed.
I'll take a look. I'm actually using my own (basic) 404 http module which is just design to improve the way .NET handles custom errors, essentially returning a page an HTTP error status code without the redirection, so I might have to make sure they play nice together or modify the source but this looks very promising.
Thanks very much :)
Hi, we have a version 8.11 project and after installing this addon I am unable to find the gadget.
Is this compatible with versions higher than 7.5?
If you're not seeing the gadget, then this bug thread might be the trick to getting this resolved - https://www.coderesort.com/p/epicode/ticket/359