https://issues.apache.org/bugzilla/show_bug.cgi?id=56618

--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> ---
Created attachment 32339
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=32339&action=edit
Initial patch with (possibly) sloppy memory management

I have a patch which lifts the whole apr_unescape_url method from APR 1.5 and
uses it in jk_status:status_parse_uri and initial testing suggests that it
works. However, I have been lazy with my memory allocations because I have not
yet understood how jk_map_put deals with memory.

I'm attaching my proposed patch with the understanding that it is almost
certainly not complete, as it likely contains a memory leak.

It also does not decode parameter *names*, but it doesn't seem like the mod_jk
status worker really needs that right now.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to