Permalink
Browse files

Update README

  • Loading branch information...
1 parent db194ab commit 7e8baf259b427335a82dfb88a34dfbfe25affaf2 @shuber shuber committed Jun 4, 2009
Showing with 2 additions and 1 deletion.
  1. +1 −0 CHANGELOG
  2. +1 −1 README.markdown
View
@@ -2,6 +2,7 @@
* Update test related rake tasks
* Remove huberry namespace
* Add support for multiple domains
+ * Update README
2009-05-20 - Sean Huber (shuber@huberry.com)
* Update date in gemspec so github rebuilds gem
View
@@ -85,7 +85,7 @@ Let's examine what this block is doing:
* If a site does exist, a new host is returned using the site's `subdomain` with your app domain and everything renders fine, otherwise...
* A fake host is returned (-INVALID-.yourcmsapp.com), and the request 404s once it gets to your `routing` controller and a site can't be found with the subdomain `-INVALID-`
-If `nil, false, or an empty string` is returned when you call the `Proxy.replace_host_with` method, the current request's host is not modified. Otherwise, the `HTTP_X_FORWARDED_HOST` request header is set to an array: `[the_original_host, the_new_host]`. This allows your routes to use your domain when evaluating routing conditions and also allows all of the application's url generators to use the original host.
+If `nil, false, or an empty string` is returned when you call the `Proxy.replace_host_with` method, the current request's host is not modified. Otherwise, the `HTTP_X_FORWARDED_HOST` request header is set to: `"#{the_original_host}, #{the_new_host}"`. This allows your routes to use your domain when evaluating routing conditions and also allows all of the application's url generators to use the original host.
## Contact

0 comments on commit 7e8baf2

Please sign in to comment.