From: Tomas Doran <bobtfish@bobtfish.net>
Date: Sat, 5 May 2012 12:37:23 +0000 (+0100)
Subject: Fix documentation for the 'secure' method in Catalyst:Request. RT#76710
X-Git-Tag: 5.90012~4
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=commitdiff_plain;h=3a526ce8805d85f0214f134af2e0a4bb107dd2d4

Fix documentation for the 'secure' method in Catalyst:Request. RT#76710
---

diff --git a/Changes b/Changes
index 261eb27..b1cc874 100644
--- a/Changes
+++ b/Changes
@@ -19,6 +19,7 @@
     directly.
   - Add note in Catalyst::Component to strongly disrecommend $self->config
   - Fix vague 'checkout' wording in Catalyst::Utils. RT#77000
+  - Fix documentation for the 'secure' method in Catalyst:Request. RT#76710
 
 5.90011 - 2012-03-08 16:43:00
 
diff --git a/lib/Catalyst/Request.pm b/lib/Catalyst/Request.pm
index 3d0c03a..d0df0f0 100644
--- a/lib/Catalyst/Request.pm
+++ b/lib/Catalyst/Request.pm
@@ -642,9 +642,8 @@ Shortcut for $req->headers->referer. Returns the referring page.
 Returns true or false, indicating whether the connection is secure
 (https). Note that the URI scheme (e.g., http vs. https) must be determined
 through heuristics, and therefore the reliability of $req->secure will depend
-on your server configuration. If you are serving secure pages on the standard
-SSL port (443) and/or setting the HTTPS environment variable, $req->secure
-should be valid.
+on your server configuration. If you are setting the HTTPS environment variable, 
+$req->secure should be valid.
 
 =head2 $req->captures