On Tue, Jul 28, 2020 at 5:40 PM Yehor Lite <egor.shvedov.98@???>
wrote:
> Hello.
>
>
>
> Faced an error in the work of the* readsocket .*
>
> *${readsocket{<name>}{<request>}{<options>}{<eol string>}{<fail string>}}*
>
>
>
> The problem arises when using the fourth argument (*{<eol string>}) *.
>
> It forcibly removes all *“\n”* from the string it receives when requested.
>
> In theory, everyone who uses *memcached* should have encountered this
> error.
>
>
>
> Example:
>
> *${readsocket{inet:MEMCACHED_HOST:MEMCACHED_PORT}{get
> $acl_c_memcache_key\r\n}{5s}{\n}}*
>
>
>
> In version 4.93 and lowest, this request will return:
>
> *"VALUE 123.123.123.123 0 21\r\ntest@??? <ntest@???>\r\nEND\r\n"*
>
>
>
> In version 4.94:
> *"VALUE 123.123.123.123 0 21\rtest@??? <rtest@???>\rEND\r"*
>
> Without “{\n}” argument, this request will return:
>
> *"VALUE 123.123.123.123 0 21\r\ntest@??? <ntest@???>\r\nEND\r\n"*
>
>
>
> The current version of exim is:
>
> # exim --version
>
> Exim version 4.94 #1 (FreeBSD 11.2) built 27-Jul-2020 15:46:45
>
>
>
> Has anyone encountered this error?
>
> Are there already existing solutions to it?
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
> www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_-1822575714604215276_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
