Kamil Dudka <kdu...@redhat.com> writes:

> +     INIT_OPT_SMART_PREFIX("ddg", "https://duckduckgo.com/?q=%s&t=elinks";),

ELinks can be built without SSL/TLS support, in which case it
will pop up an error message when asked to open an https URL.
This may be why all the other prefixes use http rather than
https.  If you want to use https whenever possible, you can do

        INIT_OPT_SMART_PREFIX("ddg", "https://duckduckgo.com/?q=%s&t=elinks";),
        INIT_OPT_SMART_PREFIX("ddg", "http://duckduckgo.com/?q=%s&t=elinks";),

However, there is a risk that the http variant might get saved to 
~/.elinks/elinks.conf, in which case ELinks will keep using that
even if the user later installs an SSL/TLS-capable ELinks binary.
Such saving happens if the user edits the rewriting rule, or if
the user sets config.saving_style = 1 or 2.  I don't know whether
this risk is so bad you'd prefer using https unconditionally.

The "t=elinks" parameter at the end makes me feel a bit uneasy.
None of the other prefix definitions has anything like that,
perhaps indicating the prefixes were added without consulting the
webmasters.  On the other hand, because ELinks by default reveals
its name in the User-Agent header, it is OK to include "t=elinks"
here too.  It might however deserve a note in the documentation
of protocol.http.user_agent:

diff --git a/src/protocol/http/http.c b/src/protocol/http/http.c
index e58c7af..14f89f8 100644
--- a/src/protocol/http/http.c
+++ b/src/protocol/http/http.c
@@ -204,7 +204,8 @@ static struct option_info http_options[] = {
                "pushing some lite version to them automagically.\n"
                "Use \" \" if you don't want any User-Agent header to be sent "
-               "at all.\n"
+               "at all. URI rewriting rules may still include parameters "
+               "that reveal you are using ELinks.\n"
                "%v in the string means ELinks version,\n"
                "%s in the string means system identification,\n"

Attachment: pgp50eJGmVGR2.pgp
Description: PGP signature

elinks-dev mailing list

Reply via email to