[jira] Updated: (TS-209) OpenSolaris: Add raw disk support for the cache
[ https://issues.apache.org/jira/browse/TS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Brezac updated TS-209: --- Attachment: trafficserver.solaris-raw.patch OpenSolaris: Add raw disk support for the cache Key: TS-209 URL: https://issues.apache.org/jira/browse/TS-209 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 2.1.0 Environment: OpenSolairs(osol0906) Reporter: George Paul Assignee: Theo Schlossnagle Fix For: 2.1.7 Attachments: trafficserver.solaris-raw.patch Currently only a file cache is supported on OpenSolaris(osol0906). Raw Disk support should be added before 2.1 release. -George -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TS-692) Allow for setting the source address for the connection to the origin server
Allow for setting the source address for the connection to the origin server
Key: TS-692
URL: https://issues.apache.org/jira/browse/TS-692
Project: Traffic Server
Issue Type: New Feature
Components: TS API
Reporter: M. Nunberg
It would be nice to have the ability to set the source address of the socket
which will connect to the origin server. Useful when fetching pages using
geo-targetting and when many different IPs are at one's disposal.
Any way would be a good way to do this, but it seems that per
http://trafficserver.apache.org/docs/v2/sdk/HTTPTransactionFunctions.html,
something like HttpTxnSourceIPSet(txn,ip) should do, but really anything should
be sufficient.
{
/*Just to be clear: under the hood, something like this should happen:*/
int sock = socket(...);
/*I need control for this line:*/
bind(sock,...);
/*Connect to the origin server*/
connect(sock,...);
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (TS-692) Allow for setting the source address for the connection to the origin server
[
https://issues.apache.org/jira/browse/TS-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-692:
Assignee: Leif Hedstrom
Allow for setting the source address for the connection to the origin server
Key: TS-692
URL: https://issues.apache.org/jira/browse/TS-692
Project: Traffic Server
Issue Type: New Feature
Components: TS API
Reporter: M. Nunberg
Assignee: Leif Hedstrom
It would be nice to have the ability to set the source address of the socket
which will connect to the origin server. Useful when fetching pages using
geo-targetting and when many different IPs are at one's disposal.
Any way would be a good way to do this, but it seems that per
http://trafficserver.apache.org/docs/v2/sdk/HTTPTransactionFunctions.html,
something like HttpTxnSourceIPSet(txn,ip) should do, but really anything
should be sufficient.
{
/*Just to be clear: under the hood, something like this should happen:*/
int sock = socket(...);
/*I need control for this line:*/
bind(sock,...);
/*Connect to the origin server*/
connect(sock,...);
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TS-642) Setting proxy.config.http.cache.http to 0 does not turn off caching
[ https://issues.apache.org/jira/browse/TS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-642. -- Resolution: Invalid So, I've tested this, and I'm fairly positive (well, 99.999% positive) that setting this setting to 0 does indeed disable HTTP caching. Note that at startup, if you have configured a cache, it will still report it. You could for example use the cache for storing your own protocol. This setting only says to never cache HTTP (which is the only protocol we handle internally). Setting proxy.config.http.cache.http to 0 does not turn off caching --- Key: TS-642 URL: https://issues.apache.org/jira/browse/TS-642 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 2.1.6, 2.1.5 Environment: Debian Linux Reporter: Marcus Clyne Assignee: Leif Hedstrom Fix For: 2.1.7 CONFIG proxy.config.http.cache.http INT 0 does not turn off caching (at least traffic.out says it's enabled). I've tested in trunk (2.1.6) as of today and version 2.1.3and 2.1.4. I tried both with traffic_cop and traffic_manager and with just traffic_server and a notice of caching being enabled was displayed in both cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TS-685) Rename partition.config ?
[ https://issues.apache.org/jira/browse/TS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003748#comment-13003748 ] Zhao Yongming commented on TS-685: -- vPartition for better user guessing CachePart for better config-codes translate, none Rename partition.config ? - Key: TS-685 URL: https://issues.apache.org/jira/browse/TS-685 Project: Traffic Server Issue Type: Improvement Components: Configuration Reporter: Leif Hedstrom Fix For: 2.1.7 The name of partitions and partition.config is somewhat unfortunate, since it's easy to confuse this with disk partitions (e.g. /dev/sda1, /dev/sdb etc.). Our partition is a logical grouping of cache storage, and has no relation to the physical disk underneath. I feel this is an area of confusion, and we could / should improve on this by renaming configurations, stats and documentation referring to partitions as something else. Suggestions for a different name would be appreciated :). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TS-685) Rename partition.config ?
[ https://issues.apache.org/jira/browse/TS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003772#comment-13003772 ] mohan_zl commented on TS-685: - Why not use cache_partition.config directly, because the structure CachePart is corresponding for one virtual partition in partition.config Rename partition.config ? - Key: TS-685 URL: https://issues.apache.org/jira/browse/TS-685 Project: Traffic Server Issue Type: Improvement Components: Configuration Reporter: Leif Hedstrom Fix For: 2.1.7 The name of partitions and partition.config is somewhat unfortunate, since it's easy to confuse this with disk partitions (e.g. /dev/sda1, /dev/sdb etc.). Our partition is a logical grouping of cache storage, and has no relation to the physical disk underneath. I feel this is an area of confusion, and we could / should improve on this by renaming configurations, stats and documentation referring to partitions as something else. Suggestions for a different name would be appreciated :). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-692) Allow for setting the source address for the connection to the origin server
[
https://issues.apache.org/jira/browse/TS-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-692:
-
Attachment: ts692.diff
This is a prototype / idea for what we could do. I'm still contemplating if we
should just bite the bullet and change the internal representation to a
sockaddr as well (instead of an int).
As been pointed out, we only (currently at least) use the IP addr of the
sockaddr.
Allow for setting the source address for the connection to the origin server
Key: TS-692
URL: https://issues.apache.org/jira/browse/TS-692
Project: Traffic Server
Issue Type: New Feature
Components: TS API
Reporter: M. Nunberg
Assignee: Leif Hedstrom
Attachments: ts692.diff
It would be nice to have the ability to set the source address of the socket
which will connect to the origin server. Useful when fetching pages using
geo-targetting and when many different IPs are at one's disposal.
Any way would be a good way to do this, but it seems that per
http://trafficserver.apache.org/docs/v2/sdk/HTTPTransactionFunctions.html,
something like HttpTxnSourceIPSet(txn,ip) should do, but really anything
should be sufficient.
{
/*Just to be clear: under the hood, something like this should happen:*/
int sock = socket(...);
/*I need control for this line:*/
bind(sock,...);
/*Connect to the origin server*/
connect(sock,...);
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-691) LogFilter not working
[ https://issues.apache.org/jira/browse/TS-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-691: - Fix Version/s: 2.1.7 LogFilter not working - Key: TS-691 URL: https://issues.apache.org/jira/browse/TS-691 Project: Traffic Server Issue Type: Bug Components: Logging Affects Versions: 2.1.6 Environment: Solaris 10, but probably others too Reporter: Igor Brezac Assignee: Leif Hedstrom Fix For: 2.1.7 Attachments: trafficserver.intfilter-fix.patch A log filter like this is not working: LogFilter Name = example/ Condition = crc MATCH ERR_CLIENT_ABORT/ Action = REJECT/ /LogFilter Fix: --- trafficserver-2.1.6-unstable/proxy/logging/LogFilter.cc 2011-02-28 12:53:23.0 -0500 +++ trafficserver-2.1.6-unstable.hack/proxy/logging/LogFilter.cc 2011-03-04 14:27:16.197395883 -0500 @@ -452,7 +452,6 @@ int64_t value; m_field-marshal(lad, (char *) value); - value = ntohl(value); // we don't use m_operator because we consider all operators to be // equivalent to MATCH for an integer field -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
