From 11549e815a0148f81018ff78649165e7de39ecfd Mon Sep 17 00:00:00 2001 From: Ryuta Kamizono Date: Thu, 3 May 2018 18:32:03 +0900 Subject: Partly revert "Use https with weblog URI" [ci skip] weblog.jamisbuck.org is not GitHub Pages. --- guides/source/routing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'guides/source') 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._ -- cgit v1.2.3