[jira] [Commented] (TS-254) Add TSEscapifyString() and TSUnescapifyString()

[James Peach (Commented) (JIRA)]

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

James Peach commented on TS-254:


FWIW, wikipedia and RFC 3986 refer to it as "Percent-Encoding". The 
CoreFoundation API on OS X refers to it as escaping ... we can probably find 
lots of example to support both nomenclatures.

> Add TSEscapifyString() and TSUnescapifyString() 
> 
>
> Key: TS-254
> URL: https://issues.apache.org/jira/browse/TS-254
> Project: Traffic Server
>  Issue Type: New Feature
>  Components: TS API
>Affects Versions: 3.0.0
>Reporter: Leif Hedstrom
>Assignee: Leif Hedstrom
>Priority: Minor
> Fix For: 3.1.4
>
>
> It would be very convenient for plugin developers to have SDK APIs that 
> allows for escaping and unescaping of strings. E.g.
> TSEscapifyString("http://www.ogre.com/ogre.png";)
>  ->  http%3A%2F%2Fwww.ogre.com%2Fogre.png
> TSUnescapifyString("http%3A%2F%2Fwww.ogre.com%2Fogre.png)
>  -> http://www.ogre.com/ogre.png
> The "unescapify" string is fairly straight forward, but the "escapify" 
> version might benefit from taking an (optional) table which describes what 
> characters needs to be escaped (e.g. in in some cases you want a / to be 
> escaped, but in others you do not).

--
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-1059) prefetch segment fault

[bettydramit (Commented) (JIRA)]

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

bettydramit commented on TS-1059:
-

is it Obsolete configuration of prefetch.config??? you can ask zwoop

> prefetch segment fault
> --
>
> Key: TS-1059
> URL: https://issues.apache.org/jira/browse/TS-1059
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP
>Affects Versions: 3.0.2
> Environment: linux(ubuntu)
>Reporter: yunfei chen
>
> I encountered a segment faut when I was testing Prefetch module。
> ab -n 1 -c 1 -X 192.168.16.198:8080 -d 
> http://club.baobao.sohu.com/r-mmbb-3954004-0-29-900.html
> configuration in records.config
>  CONFIG proxy.config.prefetch.prefetch_enabled INT 1
> configuration in prefetch.config
>  prefetch_children 192.168.16.198
>  html_tag img src
> #0  0x08124f17 in VIO::reenable (this=0x0) at 
> ../iocore/eventsystem/P_VIO.h:123
> #1  0x08147fe3 in KeepAliveConn::append (this=0xab9aef20, rdr=0x9c91b794) at 
> Prefetch.cc:1984
> #2  0x08145fd7 in KeepAliveConnTable::append (this=0xb2393608, ip=16777343, 
> buf=0x9c91b780, reader=0x9c91b794) at Prefetch.cc:2039
> #3  0x0814679b in KeepAliveLockHandler::handleEvent (this=0xb23e0b30, 
> event=2, data=0x8ab2f60) at Prefetch.cc:2168
> #4  0x08104ba5 in Continuation::handleEvent (this=0xb23e0b30, event=2, 
> data=0x8ab2f60)
> at ../iocore/eventsystem/I_Continuation.h:146
> #5  0x0830a9f5 in EThread::process_event (this=0xb7396008, e=0x8ab2f60, 
> calling_code=2) at UnixEThread.cc:140
> #6  0x0830add5 in EThread::execute (this=0xb7396008) at UnixEThread.cc:217
> #7  0x0830900e in spawn_thread_internal (a=0x895eed8) at Thread.cc:88
> #8  0x00165cc9 in start_thread (arg=0xb6f91b70) at pthread_create.c:304
> #9  0x0066f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
> #0  0x08124f17 in VIO::reenable (this=0x0) at 
> ../iocore/eventsystem/P_VIO.h:123
> #1  0x08147fe3 in KeepAliveConn::append (this=0xa5736888, rdr=0x8d0b2f4) at 
> Prefetch.cc:1984
> #2  0x08145fd7 in KeepAliveConnTable::append (this=0xb2393608, ip=16777343, 
> buf=0x8d0b2e0, reader=0x8d0b2f4) at Prefetch.cc:2039
> #3  0x08141db3 in PrefetchUrlBlaster::udpUrlBlaster (this=0x8abd3e0, 
> event=3300, data=0x0) at Prefetch.cc:885
> #4  0x0813e4ea in PrefetchUrlBlaster::init (this=0x8abd3e0, 
> list_head=0xabc59ac0, u_proto=TCP_BLAST) at Prefetch.h:280
> #5  0x08147806 in BlasterUrlList::invokeUrlBlaster (this=0xa7c22260) at 
> Prefetch.h:287
> #6  0x08141ac8 in BlasterUrlList::handleEvent (this=0xa7c22260, event=3302, 
> data=0xabc59ac0) at Prefetch.cc:803
> #7  0x08143c89 in PrefetchBlaster::handleEvent (this=0xa5739920, event=2, 
> data=0x0) at Prefetch.cc:1420
> #8  0x08144f42 in PrefetchBlaster::invokeBlaster (this=0xa5739920) at 
> Prefetch.cc:1769
> #9  0x08143e22 in PrefetchBlaster::handleEvent (this=0xa5739920, event=1102, 
> data=0xb23cdca0) at Prefetch.cc:1448
> #10 0x08104ba5 in Continuation::handleEvent (this=0xa5739920, event=1102, 
> data=0xb23cdca0)
> at ../iocore/eventsystem/I_Continuation.h:146
> #11 0x082c1abf in CacheVC::callcont (this=0xb23cdca0, event=1102) at 
> P_CacheInternal.h:629
> #12 0x082c1487 in CacheVC::openReadStartHead (this=0xb23cdca0, event=3900, 
> e=0x0) at CacheRead.cc:1115
> #13 0x08104ba5 in Continuation::handleEvent (this=0xb23cdca0, event=3900, 
> data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
> #14 0x082c1431 in CacheVC::openReadStartHead (this=0xb23cdca0, event=2, 
> e=0x8ab48a0) at CacheRead.cc:1112
> #15 0x08104ba5 in Continuation::handleEvent (this=0xb23cdca0, event=2, 
> data=0x8ab48a0)
> at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x0830a9f5 in EThread::process_event (this=0xb7295008, e=0x8ab48a0, 
> calling_code=2) at UnixEThread.cc:140
> #17 0x0830add5 in EThread::execute (this=0xb7295008) at UnixEThread.cc:217
> #18 0x0830900e in spawn_thread_internal (a=0x895dd00) at Thread.cc:88
> #19 0x00165cc9 in start_thread (arg=0xb6e90b70) at pthread_create.c:304
> #20 0x0066f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

--
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