A small patch that does 3 things:- Allow https:// Obviously won't work if curl is not compiled with SSL support,perhaps something like this could be put in: int ecore_con_url_supports_https(){ curl_version_info_data *curl_info = curl_version_info(CURLVERSION_NOW);
if(curl_info->features & CU
As I previously discussed, I did have some issue with evas_render not
being called when my computer receive data too fast. The problem was
the handling of the download prevented ecore to go into idle and call
evas_render.
To fix this, this patch change the way the fd handler is used. When
some cur
Hi,
Here is a small patch that removes the default timeout for a Curl request.
The CURLOPT_TIMEOUT option is used to set a maximum time that
Curl is allowed to perform a request.
Setting it by default makes Ecore_Con_Url (and ecore_file_download)
to fail downloading big files that takes more than
On Fri, 7 Mar 2008 15:30:07 +0100 "Cedric BAIL" <[EMAIL PROTECTED]> babbled:
> As I previously discussed, I did have some issue with evas_render not
> being called when my computer receive data too fast. The problem was
> the handling of the download prevented ecore to go into idle and call
> evas
On Mon, Mar 10, 2008 at 03:43:04AM +1100, Carsten Haitzler wrote:
> On Fri, 7 Mar 2008 15:30:07 +0100 "Cedric BAIL" <[EMAIL PROTECTED]> babbled:
>
> > As I previously discussed, I did have some issue with evas_render not
> > being called when my computer receive data too fast. The problem was
> >
On Mon, 10 Mar 2008 17:28:55 +0100 [EMAIL PROTECTED] (Lars Munch) babbled:
fixed :)
> On Mon, Mar 10, 2008 at 03:43:04AM +1100, Carsten Haitzler wrote:
> > On Fri, 7 Mar 2008 15:30:07 +0100 "Cedric BAIL" <[EMAIL PROTECTED]>
> > babbled:
> >
> > > As I previously discussed, I did have some issue
Almost :) The function _ecore_file_download_abort is still enclosed in the
HAVE_CURL ifdef.
The attached patch fixes the ramaining issue.
Regards
Lars Munch
On Tue, Mar 11, 2008 at 02:38:07PM +1100, Carsten Haitzler wrote:
> On Mon, 10 Mar 2008 17:28:55 +0100 [EMAIL PROTECTED] (Lars Munch) babbl
On Tue, 11 Mar 2008 09:30:51 +0100 [EMAIL PROTECTED] (Lars Munch) babbled:
now try :)
> Almost :) The function _ecore_file_download_abort is still enclosed in the
> HAVE_CURL ifdef.
>
> The attached patch fixes the ramaining issue.
>
> Regards
> Lars Munch
>
> On Tue, Mar 11, 2008 at 02:38:07P
On Mon, 21 Feb 2011 00:20:16 +0100 Raoul Hecky said:
in svn! tnx!
> Hi,
>
> Here is a small patch that removes the default timeout for a Curl request.
> The CURLOPT_TIMEOUT option is used to set a maximum time that
> Curl is allowed to perform a request.
> Setting it by default makes Ecore_Con_
Hi,
Here is a patch that adds a function to enable or disable libcurl verification
of
the peer's certificate authenticity. It's usefull to disable it when you do
requests to web servers with sefl-signed certificates.
The attached patch adds the function to the API.
Please apply.
--
Dear all,
There existed two problems when using ecore_con_url. We cannot set
proxy and set timeout.
So, I added two APIs for solving these problems.
Proxy can be set by setting libcurl option.
Timeout also can be set but It need to add handler for Linux alarm
signal. (Please refer:
http://curl.ha
This patch adds to ecore_con_url the ability to insert additional headers
for POST messages. It is basically two functions (add() and clear()) because
that's what I need for now, but I think the correct API should be add(),
del(), clear() (which I'll try to contribute in the near future, but not
hi
On Mon, Feb 28, 2011 at 11:41 AM, Raoul Hecky wrote:
> Here is a patch that adds a function to enable or disable libcurl
> verification of
> the peer's certificate authenticity. It's usefull to disable it when you do
> requests to web servers with sefl-signed certificates.
>
> The attached patch
On Fri, Dec 16, 2011 at 9:48 AM, Bluezery wrote:
> Dear all,
>
>
> There existed two problems when using ecore_con_url. We cannot set
> proxy and set timeout.
> So, I added two APIs for solving these problems.
> Proxy can be set by setting libcurl option.
> Timeout also can be set but It need to a
On Fri, 16 Dec 2011 17:48:42 +0900 Bluezery said:
> Dear all,
why do we need to set proxy - curl inherits $http_proxy and $https_proxy env
vars so it will use the system proxy settings... ?
>
> There existed two problems when using ecore_con_url. We cannot set
> proxy and set timeout.
> So, I
2011/12/16 Carsten Haitzler :
> why do we need to set proxy - curl inherits $http_proxy and $https_proxy env
> vars so it will use the system proxy settings... ?
>
Yes, environment value can do that in normal environment.
But each application may want to use it's own proxy.
For example, proxy byp
On Fri, 16 Dec 2011 19:41:21 +0900 Bluezery said:
> 2011/12/16 Carsten Haitzler :
> > why do we need to set proxy - curl inherits $http_proxy and $https_proxy env
> > vars so it will use the system proxy settings... ?
> >
>
> Yes, environment value can do that in normal environment.
> But each a
I fixed doc & ChangeLog & News.
2011/12/16 Carsten Haitzler :
>
> if they want to dynamically adjust the feature should be in ecore_con to track
> the changes and adjust automatically :)
--
BRs,
Kim.
Index: src/lib/ecore_con/ecore_con_url.c
===
Hi,
I merged with recent revision.
Please review this :p.
2011/12/16 Bluezery :
> I fixed doc & ChangeLog & News.
>
> 2011/12/16 Carsten Haitzler :
>>
>> if they want to dynamically adjust the feature should be in ecore_con to
>> track
>> the changes and adjust automatically :)
>
> --
> BRs,
> K
On Mon, 19 Dec 2011 18:07:10 +0900 Bluezery said:
ecore_con_url_proxy_set() should return Eina_Bool (EINA_TRUE for success,
EINA_FALSE for failure).
> Hi,
>
> I merged with recent revision.
> Please review this :p.
>
> 2011/12/16 Bluezery :
> > I fixed doc & ChangeLog & News.
> >
> > 2011/12/1
2011/12/20 Carsten Haitzler :
> On Mon, 19 Dec 2011 18:07:10 +0900 Bluezery said:
>
> ecore_con_url_proxy_set() should return Eina_Bool (EINA_TRUE for success,
> EINA_FALSE for failure).
I implemented ecore_con_url_proxy_set() similar to ecore_con_url_ssl_ca_set().
But returning Eina_Bool is more
On Wed, 21 Dec 2011 13:46:18 +0900 Bluezery said:
> 2011/12/20 Carsten Haitzler :
> > On Mon, 19 Dec 2011 18:07:10 +0900 Bluezery said:
> >
> > ecore_con_url_proxy_set() should return Eina_Bool (EINA_TRUE for success,
> > EINA_FALSE for failure).
>
> I implemented ecore_con_url_proxy_set() simi
Hello,
This new version of the patch also enables ecore_con_url to make custom HTTP
requests (such as HEAD, SUBSCRIBE, UNSUBSCRIBE and other obscure stuff).
On Thu, Aug 6, 2009 at 5:59 PM, Andre Dieb wrote:
> This patch adds to ecore_con_url the ability to insert additional headers
> for POST me
On Mon, Aug 10, 2009 at 11:19 PM, Andre
Dieb wrote:
> This new version of the patch also enables ecore_con_url to make custom HTTP
> requests (such as HEAD, SUBSCRIBE, UNSUBSCRIBE and other obscure stuff).
Ok, it's in svn.
I have just a question regarding the possible leak of the headers
structur
André, did you investigated this any further? I guess cedric is
correct and we'd need to check for headers.
On Wed, Aug 12, 2009 at 6:48 AM, Cedric BAIL wrote:
> On Mon, Aug 10, 2009 at 11:19 PM, Andre
> Dieb wrote:
>> This new version of the patch also enables ecore_con_url to make custom HTTP
>>
Hello,
As you guys noticed, the code was forcing headers = NULL without destroying
it (maybe some precaution for preventing mixed headers on successive send()
calls).
As send() cleans headers on the beginning and destroy() frees the list, we
may not set it to NULL. If the user finishes using and
Stupid me, those free() are absurdly wrong, there are no leaks there.
Attached patch fixes the header leaks.
On Thu, Aug 13, 2009 at 4:02 PM, Andre Dieb wrote:
> Hello,
>
> As you guys noticed, the code was forcing headers = NULL without destroying
> it (maybe some precaution for preventing mi
Hello,
With the ecore_con_url module, an application can take advantage of
SSL/TLS connections (using HTTPS requests for instance) in order to
exchange sensitive data with a server. However, the connection will
always fail if the server certificate isn't signed by a certificate
authority (CA)
On Thursday 30 December 2010 14:32:30 PnB wrote:
> Hello,
>
> With the ecore_con_url module, an application can take advantage of
> SSL/TLS connections (using HTTPS requests for instance) in order to
> exchange sensitive data with a server. However, the connection will
> always fail if the server
On Thu, 30 Dec 2010 15:16:47 -0200
Raphael Kubo da Costa wrote:
> On Thursday 30 December 2010 14:32:30 PnB wrote:
> > Hello,
> >
> > With the ecore_con_url module, an application can take advantage of
> > SSL/TLS connections (using HTTPS requests for instance) in order to
> > exchange sensitive
Le 30/12/2010 18:16, Raphael Kubo da Costa a écrit :
From what I see, it will replace the CA bundle it originally uses, right?
Doesn't it mean the original certificates will not be read anymore?
Yes. But it only affects the ecore_con_url you set it on, so it
shouldn't break anything I guess. I
On Thu, 30 Dec 2010, PnB wrote:
Le 30/12/2010 18:16, Raphael Kubo da Costa a écrit :
From what I see, it will replace the CA bundle it originally uses, right?
Doesn't it mean the original certificates will not be read anymore?
Yes. But it only affects the ecore_con_url you set it on, so it
Le 30/12/2010 22:10, Vincent Torri a écrit :
> http://en.wikipedia.org/wiki/Software_release_life_cycle#Beta
> http://en.wikipedia.org/wiki/Feature_complete
>
> so:
>
> * testing
> * bug fixing
>
> anything else is postponed after the release.
Thanks for the clarification. I'll wait then.
--
PnB
On Fri, 31 Dec 2010 08:18:40 +0100 PnB said:
> Le 30/12/2010 22:10, Vincent Torri a écrit :
> > http://en.wikipedia.org/wiki/Software_release_life_cycle#Beta
> > http://en.wikipedia.org/wiki/Feature_complete
> >
> > so:
> >
> > * testing
> > * bug fixing
> >
> > anything else is postponed after t
34 matches
Mail list logo
