From: Robert Pluim <rpluim@gmail.com>
To: 58925@debbugs.gnu.org
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>
Subject: bug#58925: 29.0.50; url-open-stream has no option pass tls options per call
Date: Mon, 31 Oct 2022 15:37:51 +0100 [thread overview]
Message-ID: <875yg0oy80.fsf@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\""'s message of "Mon, 31 Oct 2022 13:35:16 +0200")
>>>>> On Mon, 31 Oct 2022 13:35:16 +0200, Björn Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> said:
Björn> While investigating who to use magit with tls client certificates
Björn> I noticed that url-open-stream has no option to pass options to
Björn> network-open-stream on a per connection basis to do thing like e.g.
Björn> request the use of tls client certificates.
Björn> If this was possible the client could be able to call url with something
Björn> like (url-http "https://example.com" 'my-cb gw-options) to pass more
Björn> options to the specific gateway that is used.
Björn> I know it is possible to use network-stream-use-client-certificates
Björn> however that might be not always as elegant to use.
Elegance is in the eye of the beholder :-)
`network-stream-use-client-certificates' lets you configure which
client certificate is used for a host via auth-source. What other
options did you have in mind?
Robert
--
next prev parent reply other threads:[~2022-10-31 14:37 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yg0oy80.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=58925@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.