Awesome stuff, look forward to being able to make use of it!
Tim.
From: sr-dev [mailto:sr-dev-bounces@lists.sip-router.org] On Behalf Of Federico Cabiddu
Sent: 27 January 2016 14:50
To: Kamailio (SER) - Development Mailing List <sr-dev(a)lists.sip-router.org>
Subject: Re: [sr-dev] http_query/Curl Async Module : custom http headers feature request
Agree, FOSDEM will be a perfect opportunity for discussing about this!
Cheers,
Federico
On Wed, Jan 27, 2016 at 3:47 PM, Olle E. Johansson
<oej@edvina.net<mailto:oej@edvina.net>> wrote:
On 27 Jan 2016, at 15:07, Waite, Hugh
<hugh.waite@xura.com<mailto:hugh.waite@xura.com>> wrote:
I should add, I had it in the pipeline for the current (non-async) curl module.
Frederico’s response is probably more what you wanted!
We should possibly have an online or Fosdem meeting to discuss this mess with two
non-compatible modules. I see many cases where I want
to use both in the same Kamailio. We really need to figure this out before release,
especially from a product marketing view :-)
/O
Hugh
From: sr-dev [mailto:sr-dev-bounces@lists.sip-router.org] On Behalf Of Waite, Hugh
Sent: 27 January 2016 13:58
To: Kamailio (SER) - Development Mailing List
Subject: Re: [sr-dev] http_query/Curl Async Module : custom http headers feature request
It’s in the pipeline already!
It is needed in the API if the xcap_client module needs to be ported.
Hugh
From: sr-dev [mailto:sr-dev-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson
Sent: 27 January 2016 13:56
To: Kamailio (SER) - Development Mailing List
Subject: Re: [sr-dev] http_query/Curl Async Module : custom http headers feature request
On 27 Jan 2016, at 14:53, Tim Chubb
<tim.chubb@voicesimplified.com<mailto:tim.chubb@voicesimplified.com>> wrote:
Hi
Would it be possible to have a means of specifying additional request headers, i.e. things
like the Authorization header, so that you would be able to make use of services which use
a token based AAA system such as OAuth.
From the cli its trivial to invoke curl with additional headers i.e. if I was to query
such a service it would simply be something like this:
curl --header "Authorization: Bearer <token>"
https://<uri<http://cp.mcafee.com/d/FZsS82gs73hJ5xZAQsTphjsdTdFEITjphhjudEEEKnusovd79Jd5CXabMVVASyyye78II3xNICSh9YoSk_1guT7undxXstVsS-yxpXn7-LPOqtTTTKLsKCyNvAn4khMWVEVWyaqRQRrLesG7DR8OJMddECQjtPtPo0eOTaSRT_Vv4cvt2UAdxejxdUob3psc2TN5N8k4a2TycMIb2N101NwGlawAk5JQwcwAes71oC68y9do2wMm0_JH83gQd2wu6212UjF4Qswg8icK83bESl70g30icxqHo97dMg5MGG6wi5Nglw6gOoEn38b0op0sow30iY1lLI2gOb0bcgaDN0FU3x8s70JUc0gdE83gA0Uzcbj2OTQ1oid7aNw2h8bkmH4no0Ef38w1h490Bc4weyj0Ui4hs5CzAw-4Mn4e0XtXyg94C8cR80iY0V5Mp0EgA0EUi4p0abf9Q38nj6wQ4wugMC8Q4gIjKYl84gQmuh0E9cH2EAmhu0syH4nY92UQod78m4wQmujcwa7wsmsb8wA2h84zwIjh70Noawa8E2wEj34gCcf80ibxJjt8BQfcBO5mUm-wafBiteF9oL6Hs_zM04SDtyW9I5-Aq83iTi9t3P9Ftd41esRxkmr-9r19K9VEw4a5Emd40Tl1I_Ph0Aq8bdQDlkQg4VPmd41fZg-d3h0X-PrzVEwzUITZ9CNNEVdHR3g6Ilendrb>>
Ideally having an optional parameter on http_request/curl_http_request where you could
provide a delimited string of additional headers, as without that sort of functionality
the usefulness of http requests is pretty limited against modern web services. If this is
already possible could someone guide me to the documentation which documents this
ability?
I don’t think that exists today, but it is a very good idea and clearly possible in
Curl.
We just need the code for it :-)
Best regards,
/Olle
________________________________
This e-mail message may contain confidential, commercial or privileged information that
constitutes proprietary information of Xura, Inc. or its subsidiaries. If you are not the
intended recipient of this message, you are hereby notified that any review, use or
distribution of this information is absolutely prohibited and we request that you delete
all copies and contact us by e-mailing
tosecurity@xura.com<mailto:security@xura.com>. Thank You.
________________________________
This e-mail message may contain confidential, commercial or privileged information that
constitutes proprietary information of Xura, Inc. or its subsidiaries. If you are not the
intended recipient of this message, you are hereby notified that any review, use or
distribution of this information is absolutely prohibited and we request that you delete
all copies and contact us by e-mailing to
security@xura.com<mailto:security@xura.com>. Thank You.
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org<mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org<mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev