Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: CURLOPT_XOAUTH2_BEARER use?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Gavin Henry via curl-library <curl-library_at_lists.haxx.se>
Date: Mon, 20 Feb 2023 14:20:12 +0000
> The code search seems to be a beta github feature: I do not have access
to it and as all betas, it may still be incomplete.
>
> Running on my local clone, I get:
>
> $ find lib include -type f | xargs grep -F CURLOPT_XOAUTH2_BEARER
> lib/easyoptions.c: {"XOAUTH2_BEARER", CURLOPT_XOAUTH2_BEARER,
CURLOT_STRING, 0},
> lib/setopt.c: case CURLOPT_XOAUTH2_BEARER:
> include/curl/typecheck-gcc.h: (option) == CURLOPT_XOAUTH2_BEARER ||
\
> include/curl/curl.h: CURLOPT(CURLOPT_XOAUTH2_BEARER,
CURLOPTTYPE_STRINGPOINT, 220),
>
>
> Thus if you include the regular libcurl header file, it'll get defined.
>
> Note that github search may have missed the definition because it's done
via a macro... only a supposition, of course!
Thanks Patrick. Yep, there's no issue with it being defined:
It's the usage of it I think is my problem? I'm not seeing a Authorization
Bearer header getting added at all.
Date: Mon, 20 Feb 2023 14:20:12 +0000
> The code search seems to be a beta github feature: I do not have access
to it and as all betas, it may still be incomplete.
>
> Running on my local clone, I get:
>
> $ find lib include -type f | xargs grep -F CURLOPT_XOAUTH2_BEARER
> lib/easyoptions.c: {"XOAUTH2_BEARER", CURLOPT_XOAUTH2_BEARER,
CURLOT_STRING, 0},
> lib/setopt.c: case CURLOPT_XOAUTH2_BEARER:
> include/curl/typecheck-gcc.h: (option) == CURLOPT_XOAUTH2_BEARER ||
\
> include/curl/curl.h: CURLOPT(CURLOPT_XOAUTH2_BEARER,
CURLOPTTYPE_STRINGPOINT, 220),
>
>
> Thus if you include the regular libcurl header file, it'll get defined.
>
> Note that github search may have missed the definition because it's done
via a macro... only a supposition, of course!
Thanks Patrick. Yep, there's no issue with it being defined:
It's the usage of it I think is my problem? I'm not seeing a Authorization
Bearer header getting added at all.
-- Kind Regards, Gavin Henry. https://sentrypeer.org
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-02-20