From 667e11c4ec3835d959aab1797647bd0a49869674 Mon Sep 17 00:00:00 2001 From: etienne Date: Tue, 21 Oct 2014 23:35:24 +0200 Subject: Init commit --- content/extras/urls.md | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 content/extras/urls.md (limited to 'content/extras/urls.md') diff --git a/content/extras/urls.md b/content/extras/urls.md new file mode 100644 index 0000000..7bfaf33 --- /dev/null +++ b/content/extras/urls.md @@ -0,0 +1,45 @@ +--- +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 ugly URLs, 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. -- cgit v1.3