does wireHttp implement CURLOPT_USERPWD

[benbyf]

Trying to rework my Stripe implementation to get up-to-date with the latest regulation changes and wanted to use wireHttp instead of simply curl, but couldnt work out at all how to add a user password along with the request.

[elabx]

Hi! Doesn't seem to be ready, I see it commented here :

https://github.com/processwire/processwire/blob/master/wire/core/WireHttp.php#L545

[dragan]

Do you really mean user:pass, as described in the docs, or do you simply have a field named username and another named pass? If the latter, you can just do regular post fields. Or try setting an Authorization: Basic header as shown here.

[benbyf]

Think i'm miss understanding the conversion between curl in the terminal and curl in php.  Looking at the below and wondered how to set the -u. Is it setting a CURLOPT_USERPWD header? Or more complex than that?

https://stripe.com/docs/payments/checkout/migration#client-products-server-code

curl https://api.stripe.com/v1/customers \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d email="{{STRIPE_EMAIL}}" \
  -d source="{{STRIPE_TOKEN}}"

[elabx]

According to here:

https://www.php.net/manual/en/function.curl-setopt.php

It does look like it's the same, those two dots at the end seem to indicate the password is coming, though stripe doesn't seem to need it.