[jira] [Commented] (TS-1188) http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf is 404

2012-04-04 Thread Eric Ahn (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246486#comment-13246486
 ] 

Eric Ahn commented on TS-1188:
--

step as follow :
1) http://trafficserver.apache.org/docs/
2) Traffic Server 管理员指南 (PDF) - click
3) message is
Not Found

The requested URL /docs/trunk/admin/ts_admin_chinese.pdf was not found on this 
server.

 http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf is 404
 

 Key: TS-1188
 URL: https://issues.apache.org/jira/browse/TS-1188
 Project: Traffic Server
  Issue Type: Bug
  Components: Web site
Reporter: James Peach
Assignee: Igor Galić
Priority: Minor

 The main docs page tries to point to the Chinese admin docs at 
 http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf, but 
 there's nothing there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TS-1187) TSMimeHdrFieldNameSet does not work for headers read from the client or origin server (but does work for headers added by traffic server)

2012-04-04 Thread Eric Ahn (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246627#comment-13246627
 ] 

Eric Ahn commented on TS-1187:
--

I just figure it out,

It set headers using TSMimeHdrFieldNameSet, looks like myheader : 
header-value.
but can't sent client or origin server.

In case of sending cache to origin server, it appears only header name, that is 
myheader : , in origin server, but, can't see value header-value.



 TSMimeHdrFieldNameSet does not work for headers read from the client or 
 origin server (but does work for headers added by traffic server)
 -

 Key: TS-1187
 URL: https://issues.apache.org/jira/browse/TS-1187
 Project: Traffic Server
  Issue Type: Bug
  Components: MIME
Affects Versions: 3.0.2
 Environment: Redhat linux with plugin that wants to rename a header 
 read from the client.
Reporter: Alistair Stevenson
  Labels: api-change
 Fix For: 3.1.4


 TSMimeHdrFieldNameSet does not work for headers read from the client or 
 origin server (but does work for headers added by traffic server)
 The name appears set (and the function returns SUCCESS) but when the data is 
 sent to the origin Server it is corrupted at the point where the header is 
 set. i.e the header name is sent but the header is corrupted after this.
 I am having to create a new header and copy the values and then destroy the 
 original header which is not as efficient.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TS-1099) review of squid replacement algorithm

2012-01-31 Thread Eric Ahn (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197158#comment-13197158
 ] 

Eric Ahn commented on TS-1099:
--

It should review for replacement algorithm to supply a various replacement 
method on ATS.

 review of squid replacement algorithm
 -

 Key: TS-1099
 URL: https://issues.apache.org/jira/browse/TS-1099
 Project: Traffic Server
  Issue Type: Sub-task
  Components: Plugins
Reporter: Eric Ahn
Priority: Minor
 Fix For: Doc 3.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TS-337) Cache Replacement Algorithm plug-in API

2012-01-31 Thread Eric Ahn (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197156#comment-13197156
 ] 

Eric Ahn commented on TS-337:
-

Leif, Is this issue plugin component?

 Cache Replacement Algorithm plug-in API
 ---

 Key: TS-337
 URL: https://issues.apache.org/jira/browse/TS-337
 Project: Traffic Server
  Issue Type: New Feature
  Components: Documentation
Affects Versions: 2.0.0
Reporter: Mark Nottingham
 Fix For: Doc 3.0


 New cache replacement algorithms are often proposed, and often it's not a 
 one size fits all problem; different workloads require different approaches.
 To facilitate this, TS should have a pluggable cache replacement policy API, 
 both for the memory and disk cache.
 Squid has done this to good effect; see
   http://www.squid-cache.org/cgi-bin/cvsweb.cgi/squid/src/repl/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TS-337) Cache Replacement Algorithm plug-in API

2012-01-30 Thread Eric Ahn (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13196109#comment-13196109
 ] 

Eric Ahn commented on TS-337:
-

squid support heap and lru replacement.

 Cache Replacement Algorithm plug-in API
 ---

 Key: TS-337
 URL: https://issues.apache.org/jira/browse/TS-337
 Project: Traffic Server
  Issue Type: New Feature
  Components: Documentation
Affects Versions: 2.0.0
Reporter: Mark Nottingham
 Fix For: Doc 3.0


 New cache replacement algorithms are often proposed, and often it's not a 
 one size fits all problem; different workloads require different approaches.
 To facilitate this, TS should have a pluggable cache replacement policy API, 
 both for the memory and disk cache.
 Squid has done this to good effect; see
   http://www.squid-cache.org/cgi-bin/cvsweb.cgi/squid/src/repl/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TS-1076) Implement the ESI for ATS

2012-01-09 Thread Eric Ahn (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182998#comment-13182998
 ] 

Eric Ahn commented on TS-1076:
--

I found homepage, 
http://trafficserver.apache.org/docs/trunk/admin/plugins/index.en.html.
and also I reviewed the plugin after checkout, svn is 
http://svn.apache.org/repos/asf/trafficserver/plugins/trunk/ 


 Implement the ESI  for ATS
 --

 Key: TS-1076
 URL: https://issues.apache.org/jira/browse/TS-1076
 Project: Traffic Server
  Issue Type: New Feature
  Components: Plugins
Affects Versions: 3.0.2
Reporter: Eric Ahn
Priority: Minor
  Labels: cache

 Support ESI feature.
 You can review the doc (http://www.akamai.com/html/support/esi.html)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira