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

**URL:** <https://discuss.elastic.co/t/invalid-redirect-in-elastic-co-blog-causes-links-to-lead-to-404/34469>\
**Category:** Meta Elastic\
**Created:** [November 12, 2015, 10:26pm UTC](https://discuss.elastic.co/t/invalid-redirect-in-elastic-co-blog-causes-links-to-lead-to-404/34469 "2015-11-12T22:26:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![igor\_k](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_k/32/1157_2.png) [@igor\_k](https://discuss.elastic.co/u/igor_k)\
**Post date:** [November 12, 2015, 10:26pm UTC](https://discuss.elastic.co/t/invalid-redirect-in-elastic-co-blog-causes-links-to-lead-to-404/34469/1 "2015-11-12T22:26:14Z")

</div>

Hi Elastic,

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

 ![](https://us1.discourse-cdn.com/elastic/original/2X/6/6d6d14a317fd6f4e63324663042c13bfa5c81682.png)

To reproduce:

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

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

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

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 12, 2015, 10:29pm UTC](https://discuss.elastic.co/t/invalid-redirect-in-elastic-co-blog-causes-links-to-lead-to-404/34469/2 "2015-11-12T22:29:54Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 17, 2015, 8:16pm UTC](https://discuss.elastic.co/t/invalid-redirect-in-elastic-co-blog-causes-links-to-lead-to-404/34469/3 "2015-11-17T20:16:39Z")

</div>

This is now fixed, thanks again!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/invalid-redirect-in-elastic-co-blog-causes-links-to-lead-to-404/34469/4 "2017-07-06T13:47:08Z")

</div>