You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Miles Libbey (JIRA)" <ji...@apache.org> on 2014/08/26 01:32:57 UTC

[jira] [Commented] (TS-3043) auth_proxy plugin doc doesn't talk about auth remap rule required

    [ https://issues.apache.org/jira/browse/TS-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109977#comment-14109977 ] 

Miles Libbey commented on TS-3043:
----------------------------------

diff --git a/doc/reference/plugins/authproxy.en.rst b/doc/reference/plugins/authproxy.en.rst
index e2241a1..c30f185 100644
--- a/doc/reference/plugins/authproxy.en.rst
+++ b/doc/reference/plugins/authproxy.en.rst
@@ -35,6 +35,12 @@ plugin. you can disable this behavior by setting
 :ts:cv:`proxy.config.http.doc_in_cache_skip_dns` to ``0`` in
 :file:`records.config`.

+Traffic Server requires a remap rule for the authorization request.
+As a result, the pristine Host header for the initial request will
+not automatically be sent. The Host header could be added using the
+``header_rewrite`` plugin (set-header Host "pristine_host.example.com").
+
+
 Plugin Options
 --------------

@@ -84,8 +90,14 @@ HTTP request to a `HEAD` request and sending that to the origin server
   map http://cache.example.com http://origin.internal.com/ \
     @plugin=authproxy.so @pparam=--auth-transform=head

+  map http://origin.internal.com http://origin.internal.com/
+
+
 In this example, the request is directed to a local authentication server
 that authorizes the request based on internal policy rules::

   map http://cache.example.com http://origin.internal.com/ \
     @plugin=authproxy.so @pparam=--auth-transform=redirect @pparam=--auth-host=127.0.0.1 @pparam=--auth-port=9000
+
+  map http://origin.internal.com/ http://origin.internal.com/ \
+    @plugin=authproxy.so @pparam=--auth-transform=redirect @pparam=--auth-host=127.0.0.1 @pparam=--auth-port=9000

> auth_proxy plugin doc doesn't talk about auth remap rule required
> -----------------------------------------------------------------
>
>                 Key: TS-3043
>                 URL: https://issues.apache.org/jira/browse/TS-3043
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Miles Libbey
>
> When using the authproxy plugin, one must configure a remap rule to handle the request that goes to the authorization server.  The current docs don't mention this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)