# Hosting on App Engine and handling alias redirects

**URL:** <https://discourse.gohugo.io/t/hosting-on-app-engine-and-handling-alias-redirects/4599>\
**Category:** support\
**Created:** [November 17, 2016, 11:04pm UTC](https://discourse.gohugo.io/t/hosting-on-app-engine-and-handling-alias-redirects/4599 "2016-11-17T23:04:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [November 18, 2016, 12:09am UTC](https://discourse.gohugo.io/t/hosting-on-app-engine-and-handling-alias-redirects/4599/3 "2016-11-18T00:09:19Z")

</div>

> [@iandouglas](#):
>
> Now I just need to get Hugo to build a file out of the aliases if config.toml says to generate .htaccess or something. Any takers?

I’m not convinced this a feature worth the implementation, maintainance and support cost. `.htaccess` is Apache format, and adding such support will soon get the Nginx and the Caddy etc. crowd shouting.

My advice would be to jump in on this:

> **[Custom output content types](https://discourse.gohugo.io/t/custom-output-content-types/4584/2)**
>
> I think this is a great idea for many reasons, not the least of which is the added flexibility for pulling from content files to create new files in serialized data formats (specifically .json). What if you skip the config piece altogether and...

The alias entries are available – and I can imagine a “htaccess” template definition would fit into my thoughts outlined in the thread above.

---

_[View the full topic](https://discourse.gohugo.io/t/hosting-on-app-engine-and-handling-alias-redirects/4599)._