You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2010/11/10 23:36:13 UTC
[jira] Created: (TS-526) Plugin API call to get effective URL for a
transaction.
Plugin API call to get effective URL for a transaction.
-------------------------------------------------------
Key: TS-526
URL: https://issues.apache.org/jira/browse/TS-526
Project: Traffic Server
Issue Type: New Feature
Components: Plugins
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Priority: Minor
For transparent proxying, the host is frequently not in the explicit URL in the request. Plugins therefore have to dig around in the MIME headers for the HOST field to be robust, when frequently all that is needed by the plugin is the effective URL, that is the full URL for the target. The logic to compute this already exists in the HTTPHdr class and it should be made available to plugins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TS-526) Plugin API call to get
effective URL for a transaction.
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931080#action_12931080 ]
Alan M. Carroll edited comment on TS-526 at 11/11/10 11:57 AM:
---------------------------------------------------------------
Comitted r1033997.
Added the following API call.
<pre>
/** Get the effective URL for the transaction.
The effective URL is the URL taking in to account both the explicit
URL in the request and the HOST field.
A possibly non-null terminated string is returned.
@note The returned string is allocated and must be freed by the caller
after use with @c INKfree.
*/
inkapi char* INKHttpTxnEffectiveUrlStringGet(
INKHttpTxn txnp, ///< Transaction.
int* length ///< String length return, may be @c NULL.
);
</pre>
was (Author: amc):
Comitted r1033997.
Added the following API call.
/** Get the effective URL for the transaction.
The effective URL is the URL taking in to account both the explicit
URL in the request and the HOST field.
A possibly non-null terminated string is returned.
@note The returned string is allocated and must be freed by the caller
after use with @c INKfree.
*/
inkapi char* INKHttpTxnEffectiveUrlStringGet(
INKHttpTxn txnp, ///< Transaction.
int* length ///< String length return, may be @c NULL.
);
> Plugin API call to get effective URL for a transaction.
> -------------------------------------------------------
>
> Key: TS-526
> URL: https://issues.apache.org/jira/browse/TS-526
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Attachments: ts-526-patch.txt
>
>
> For transparent proxying, the host is frequently not in the explicit URL in the request. Plugins therefore have to dig around in the MIME headers for the HOST field to be robust, when frequently all that is needed by the plugin is the effective URL, that is the full URL for the target. The logic to compute this already exists in the HTTPHdr class and it should be made available to plugins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-526) Plugin API call to get effective URL for a
transaction.
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll updated TS-526:
-------------------------------
Attachment: ts-526-patch.txt
> Plugin API call to get effective URL for a transaction.
> -------------------------------------------------------
>
> Key: TS-526
> URL: https://issues.apache.org/jira/browse/TS-526
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Attachments: ts-526-patch.txt
>
>
> For transparent proxying, the host is frequently not in the explicit URL in the request. Plugins therefore have to dig around in the MIME headers for the HOST field to be robust, when frequently all that is needed by the plugin is the effective URL, that is the full URL for the target. The logic to compute this already exists in the HTTPHdr class and it should be made available to plugins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-526) Plugin API call to get effective URL for a
transaction.
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll updated TS-526:
-------------------------------
Fix Version/s: 2.1.5
> Plugin API call to get effective URL for a transaction.
> -------------------------------------------------------
>
> Key: TS-526
> URL: https://issues.apache.org/jira/browse/TS-526
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Fix For: 2.1.5
>
> Attachments: ts-526-patch.txt
>
>
> For transparent proxying, the host is frequently not in the explicit URL in the request. Plugins therefore have to dig around in the MIME headers for the HOST field to be robust, when frequently all that is needed by the plugin is the effective URL, that is the full URL for the target. The logic to compute this already exists in the HTTPHdr class and it should be made available to plugins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TS-526) Plugin API call to get
effective URL for a transaction.
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931080#action_12931080 ]
Alan M. Carroll edited comment on TS-526 at 11/11/10 11:59 AM:
---------------------------------------------------------------
Comitted r1033997.
Added the following API call.
{noformat}
/** Get the effective URL for the transaction.
The effective URL is the URL taking in to account both the explicit
URL in the request and the HOST field.
A possibly non-null terminated string is returned.
@note The returned string is allocated and must be freed by the caller
after use with @c INKfree.
*/
inkapi char* INKHttpTxnEffectiveUrlStringGet(
INKHttpTxn txnp, ///< Transaction.
int* length ///< String length return, may be @c NULL.
);
{noformat}
was (Author: amc):
Comitted r1033997.
Added the following API call.
<pre>
/** Get the effective URL for the transaction.
The effective URL is the URL taking in to account both the explicit
URL in the request and the HOST field.
A possibly non-null terminated string is returned.
@note The returned string is allocated and must be freed by the caller
after use with @c INKfree.
*/
inkapi char* INKHttpTxnEffectiveUrlStringGet(
INKHttpTxn txnp, ///< Transaction.
int* length ///< String length return, may be @c NULL.
);
</pre>
> Plugin API call to get effective URL for a transaction.
> -------------------------------------------------------
>
> Key: TS-526
> URL: https://issues.apache.org/jira/browse/TS-526
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Attachments: ts-526-patch.txt
>
>
> For transparent proxying, the host is frequently not in the explicit URL in the request. Plugins therefore have to dig around in the MIME headers for the HOST field to be robust, when frequently all that is needed by the plugin is the effective URL, that is the full URL for the target. The logic to compute this already exists in the HTTPHdr class and it should be made available to plugins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.