aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/routing.md
diff options
context:
space:
mode:
authorRyuta Kamizono <kamipo@gmail.com>2018-05-03 18:32:03 +0900
committerRyuta Kamizono <kamipo@gmail.com>2018-05-03 18:32:03 +0900
commit11549e815a0148f81018ff78649165e7de39ecfd (patch)
tree793f2ac074b7f32eb279e4b7cef343829357d568 /guides/source/routing.md
parent1007191f31d7ce8486f1f32a5d700bbac66ae242 (diff)
downloadrails-11549e815a0148f81018ff78649165e7de39ecfd.tar.gz
rails-11549e815a0148f81018ff78649165e7de39ecfd.tar.bz2
rails-11549e815a0148f81018ff78649165e7de39ecfd.zip
Partly revert "Use https with weblog URI" [ci skip]
weblog.jamisbuck.org is not GitHub Pages.
Diffstat (limited to 'guides/source/routing.md')
-rw-r--r--guides/source/routing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/routing.md b/guides/source/routing.md
index 887e23e670..7a83fee617 100644
--- a/guides/source/routing.md
+++ b/guides/source/routing.md
@@ -316,7 +316,7 @@ Deeply-nested resources quickly become cumbersome. In this case, for example, th
/publishers/1/magazines/2/photos/3
```
-The corresponding route helper would be `publisher_magazine_photo_url`, requiring you to specify objects at all three levels. Indeed, this situation is confusing enough that a popular [article](https://weblog.jamisbuck.org/2007/2/5/nesting-resources) by Jamis Buck proposes a rule of thumb for good Rails design:
+The corresponding route helper would be `publisher_magazine_photo_url`, requiring you to specify objects at all three levels. Indeed, this situation is confusing enough that a popular [article](http://weblog.jamisbuck.org/2007/2/5/nesting-resources) by Jamis Buck proposes a rule of thumb for good Rails design:
TIP: _Resources should never be nested more than 1 level deep._