diff options
| author | Yoshiyuki Hirano <yhirano@me.com> | 2018-05-02 21:06:03 +0900 |
|---|---|---|
| committer | Yoshiyuki Hirano <yhirano@me.com> | 2018-05-02 21:06:03 +0900 |
| commit | f3c71ff1e18369bf15ab9b51e448644ea2c2c349 (patch) | |
| tree | 8d2fc3046fe4626ce88426834df824d5f2319d82 /guides/source/routing.md | |
| parent | e9f434d3aab9ca457613cc08c3857879d949cbc0 (diff) | |
| download | rails-f3c71ff1e18369bf15ab9b51e448644ea2c2c349.tar.gz rails-f3c71ff1e18369bf15ab9b51e448644ea2c2c349.tar.bz2 rails-f3c71ff1e18369bf15ab9b51e448644ea2c2c349.zip | |
Use https with weblog URI
Diffstat (limited to 'guides/source/routing.md')
| -rw-r--r-- | guides/source/routing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/routing.md b/guides/source/routing.md index 7a83fee617..887e23e670 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](http://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](https://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._ |