unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>, 58925@debbugs.gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#58925: 29.0.50; url-open-stream has no option pass tls options per call
Date: Mon, 31 Oct 2022 08:02:53 -0700	[thread overview]
Message-ID: <CADwFkmntWDxP8s3PmXN-6JcnXk1rnHfeXdd+A1ZWERq_6d1ECA@mail.gmail.com> (raw)
In-Reply-To: <87pme8b4zv.fsf@thaodan.de>

Björn Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:

> While investigating who to use magit with tls client certificates
> I noticed that url-open-stream has no option to pass options to
> network-open-stream on a per connection basis to do thing like e.g.
> request the use of tls client certificates.
>
> If this was possible the client could be able to call url with something
> like (url-http "https://example.com" 'my-cb gw-options) to pass more
> options to the specific gateway that is used.
>
> I know it is possible to use network-stream-use-client-certificates
> however that might be not always as elegant to use.

I think this is a general problem with url.el: there are many things
that you can basically only change by let-binding some variable.
So while this setting is important, there are other things that are
important too.

In any case, improving the url.el seems like the wrong thing to work on,
when we should instead be working on replacing it.  I think the most
promising direction is integrating libcurl, myself.  Let's remember that
url.el is both old and stable.

So I'd be inclined to close this as wontfix.





      parent reply	other threads:[~2022-10-31 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 11:35 bug#58925: 29.0.50; url-open-stream has no option pass tls options per call Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-31 14:37 ` Robert Pluim
2022-11-01 10:53   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-12 20:34     ` Stefan Kangas
2022-11-13 14:37       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-31 15:02 ` Stefan Kangas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmntWDxP8s3PmXN-6JcnXk1rnHfeXdd+A1ZWERq_6d1ECA@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=58925@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).