hugo/docs/content/extras/urls.md

46 lines
1.4 KiB
Markdown
Raw Normal View History

---
aliases:
2014-05-29 18:42:05 -04:00
- /doc/urls/
date: 2014-01-03
menu:
main:
2014-05-29 18:42:05 -04:00
parent: extras
next: /community/mailing-list
notoc: true
prev: /extras/toc
title: URLs
weight: 70
---
2014-02-20 19:04:29 -05:00
## Pretty Urls
By default Hugo will create content with 'pretty' urls. For example
content created at /content/extras/urls.md will be rendered at
/content/extras/urls/index.html and accessible at /content/extras/urls. No
no standard server side configuration is required for these pretty urls to
work.
2014-02-20 19:04:29 -05:00
If you would like to have uglyurls you are in luck. Hugo supports the
ability to create your entire site with ugly urls. Simply use the
`--uglyurls=true` flag on the command line.
If you want a specific piece of content to have an exact url you can
specify this in the front matter under the url key. See [Content
2014-05-09 11:32:06 -04:00
Organization](/content/organization/) for more details.
2014-02-20 19:04:29 -05:00
## Canonicalization
By default, all relative URLs encountered in the input will be canonicalized
using `baseurl`, so that a link `/css/foo.css` becomes
`http://yoursite.example.com/css/foo.css`.
Setting `canonifyurls` to `false` will prevent this canonicalization.
Benefits of canonicalization include fixing all URLs to be absolute, which may
aid with some parsing tasks. Note though that all real browsers handle this
client-side without issues.
Benefits of non-canonicalization include being able to have resource inclusion
be scheme-relative, so that http vs https can be decided based on how this
page was retrieved.