You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nginx-xml2pod: ensured <link> tags contents are parsed.
In recent nginx 1.15.8 documentation, the following XML document:
<module name="Module ngx_stream_proxy_module"
link="/en/docs/stream/ngx_stream_proxy_module.html">
<para>
Enables terminating all sessions to a proxied server
after it was removed from the group or marked as permanently unavailable.
This can occur because of
<link doc="ngx_stream_core_module.xml" id="resolver">re-resolve</link>
or with the API
<link doc="../http/ngx_http_api_module.xml" id="deleteStreamUpstreamServer"><literal>DELETE</literal></link>
command.
</para>
</module>
Would produce this output:
Enables terminating all sessions to a proxied server
after it was removed from the group or marked as permanently unavailable.
This can occur because of
L<re-resolve|ngx_stream_core_module>
or with the API
L<E<ltE<gt>literalE<gt>DELETEE<ltE<gt>E<sol>literalE<gt>|ngx_http_api_module>
command.
Thanks to this patch, the output is now:
Enables terminating all sessions to a proxied server
after it was removed from the group or marked as permanently unavailable.
This can occur because of
L<re-resolve|ngx_stream_core_module>
or with the API
L<C<DELETE>|ngx_http_api_module>
command.
Note that now, links can contain nested markup as well.
---
We also modified the parsing of `\&\w+;` subjects (i.e. `“`) to
void a regression in the parsing of `welcome_nginx_facebook.pod`.
The input:
<link url="http://www.dcwg.org/fix/">
How to clean up or fix malicious software (“malware”)
associated with DNS Changer
</link>
The (invalid) output without this change would be:
L<How to clean up or fix malicious software (E<ldquo>malwareE<rdquo>) ... >
Since we removed the `encode_pod()` call on the link's contents.
The correct output is instead:
L<How to clean up or fix malicious software (E<amp>ldquo;malwareE<amp>rdquo;) ...>
So we forced the `encode_pod()` call when this subject is parsed
_inside_ of a link's contents.
0 commit comments