Invalid redirect in elastic.co/blog causes links to lead to 404


(Igor KupczyƄski) #1

Hi Elastic,

This is a page I've encountered while browsing your blog posts.

To reproduce:

  1. Go to https://www.elastic.co/blog/found-elasticsearch-plugin-types

  2. Click any internal link to other elastic/found blog article, e.g.

    Elasticsearch Internals: An Overview
    Do notice the trailing slash

  3. GET /blog/found-writing-a-plugin/ results in 302 Moved Temporarily to blog/found-writing-a-plugin (no leading and no trailing slashes).

The browser interprets this as a relative path to be added to the current path, i.e. https://www.elastic.co/blog/found-writing-a-plugin/blog/found-writing-a-plugin

I saw this only on found blog posts. Probably this is a migration issue.

To fix I think you need to change the nginx rewrite rule to include the leading slash. Or at very least drop the trailing slash from the links in the posts.

Cheers,
Igor


(Mark Walkom) #2

Thanks, I will make our content team aware of this!


(Mark Walkom) #3

This is now fixed, thanks again!


(system) #4