hugo/docs/content/extras/urls.md

---
aliases:
- /doc/urls/
date: 2014-01-03
menu:
  main:
    parent: extras
next: /community/mailing-list
notoc: true
prev: /extras/toc
title: URLs
weight: 70
---

## 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.

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
Organization](/content/organization/) for more details. 

## 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.
Add `canonifyurls` config option. Be able to inhibit AbsURL canonicalization of content, on a site configuration basis. Advantages of being able to inhibit this include making it easier to rendering on other hostnames, and being able to include resources on http or https depending on how this page was retrieved, avoiding mixed-mode client complaints without adding latency for plain http. 2014-01-03 23:36:53 +00:00			`---`
			`aliases:`
Converting front matter to YAML 2014-05-29 22:42:05 +00:00			`- /doc/urls/`
			`date: 2014-01-03`
Implementing new menu system in the docs site 2014-04-23 07:00:11 +00:00			`menu:`
			`main:`
Converting front matter to YAML 2014-05-29 22:42:05 +00:00			`parent: extras`
			`next: /community/mailing-list`
			`notoc: true`
			`prev: /extras/toc`
			`title: URLs`
			`weight: 70`
Add `canonifyurls` config option. Be able to inhibit AbsURL canonicalization of content, on a site configuration basis. Advantages of being able to inhibit this include making it easier to rendering on other hostnames, and being able to include resources on http or https depending on how this page was retrieved, avoiding mixed-mode client complaints without adding latency for plain http. 2014-01-03 23:36:53 +00:00			`---`
Adding documentation on Pretty Urls 2014-02-21 00:04:29 +00: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`
Updating / Rewriting / Adding all of the documentation in preparation for the next release 2014-05-27 22:32:57 +00:00			`work.`
Adding documentation on Pretty Urls 2014-02-21 00:04:29 +00: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`
Fixing broken link. Fixed #278. 2014-05-09 15:32:06 +00:00			`Organization](/content/organization/) for more details.`
Adding documentation on Pretty Urls 2014-02-21 00:04:29 +00:00
			`## Canonicalization`

Add `canonifyurls` config option. Be able to inhibit AbsURL canonicalization of content, on a site configuration basis. Advantages of being able to inhibit this include making it easier to rendering on other hostnames, and being able to include resources on http or https depending on how this page was retrieved, avoiding mixed-mode client complaints without adding latency for plain http. 2014-01-03 23:36:53 +00:00			`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.`