Re: rfc1738.c
Damian Wojslaw <[email protected]>
| Newsgroups | gmane.comp.web.squid.devel |
|---|---|
| Message-ID | <CAKh_g9GypYN925U7D2Bhk5Z+_=9Ghr_JVWMYj_P_DM6_fEsqbg@mail.gmail.com> |
On Thu, Oct 29, 2020 at 12:49 PM Amos Jeffries <[email protected]> wrote: > > The latest Squid have AnyP::Uri::Encode() whic uses a caller provided > buffer. What needs doing now is finding old rfc1738*_escape() which can > be replaced with the new API. > > For example; code like urlCanonicalCleanWithoutRequest() where the data > is stored in an SBuf, but converted to char* in order to use the rfc1738 > API. > > Also a AnyP::Uri::Decode function needs adding so we can convert the > rfc1738_*unescape() callers too. > Ok, I'll get myself familiar with that. > The cachemgr.cc code is "neglected" primarily because it is deprecated. > It has been replaced by reports served directly in HTTP by the proxy. > Thank you > Amos > -- Damian Wojsław He/Him/His Software Maintenance Engineer EMEA irc: madwizard @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> _______________________________________________ squid-dev mailing list [email protected] http://lists.squid-cache.org/listinfo/squid-dev