Re: default CA cert bundle/path - not working

On Fri, 30 Mar 2012, curl.bullrunner <at> spamgourmet.com wrote:

> I know it is probably a matter of opinion, but I would say there is a 
> shortcoming in this case in either the configure script or the 
> documentation. After battling for days with one obstacle after another, 
> admittedly on a steep learning, to be tripped up by something as simple as 
> this is a little frustrating. Hopefully we can spare a few people from 
> having to learn the hard way in future.

So, ok, after having finally won against configure in this battle, where do 
you think the problem is mostly? In the documentation or in the script? I 
mean, after having finally made it work do you have any suggestions on what we 
should change to make it less cumbersome the next time someone else enters 
your situation?

> PS. Any idea how I can create a binary package out of my cURL build?

See packages/AIX/RPM/README for one way. If that's not good enough, I figure 
you need to find some AIX docs on how to make packages...

--

-- 

  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

simplified progress-bar for dumb terminals

Hello,

dracut developers are asking us to implement a simplified progress bar that 
would be similar to the output of --progress-bar but compatible with terminals 
that do not support the '\r' character:

https://bugzilla.redhat.com/show_bug.cgi?id=806426

Does such an enhancement make sense?  Would it be accepted upstream?

Kamil
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

转发： About headers with no contents.

----- 原始消息 -----
发件人： Jason Liu
收件人： 'curl-library <at> cool.haxx.se' <curl-library <at> cool.haxx.se>
发送时间： Sun Apr 01 03:57:31 2012
主题： About headers with no contents.

Hi
I want to send a request with headers like "Empty-header:".
But libcurl can only send this header like "Empty-header:""". Many sites don't consider this header right
and return 400.

So how can I send as "Empty-header:"?

Thank you very much!

Jason Liu

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged
material (including material protected by the solicitor-client or other applicable privileges), or
constitute non-public information. Any use of this information by anyone other than the intended
recipient is prohibited. If you have received this transmission in error, please immediately reply to
the sender and delete this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Re: 转发： About headers with no contents.

On Mon, Apr 02, 2012 at 08:46:41AM -0400, Jason Liu wrote:
> I want to send a request with headers like "Empty-header:".
> But libcurl can only send this header like "Empty-header:""". Many sites don't consider this header
right and return 400.
> 
> So how can I send as "Empty-header:"?

Since version 7.23.0, you can send an empty header by changing the colon to
a semicolon, i.e. Empty-header; is converted and sent as Empty-header:

>>> Dan
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

答复： Re: 转发： About headers with no contents.

I will have a try.
Thank you very much.

----- 原始消息 -----
发件人： curl-users-bounces <at> cool.haxx.se <curl-users-bounces <at> cool.haxx.se>
收件人： curl-users <at> cool.haxx.se <curl-users <at> cool.haxx.se>
发送时间： Mon Apr 02 09:00:40 2012
主题： Re: 转发： About headers with no contents.

On Mon, Apr 02, 2012 at 08:46:41AM -0400, Jason Liu wrote:
> I want to send a request with headers like "Empty-header:".
> But libcurl can only send this header like "Empty-header:""". Many sites don't consider this header
right and return 400.
> 
> So how can I send as "Empty-header:"?

Since version 7.23.0, you can send an empty header by changing the colon to
a semicolon, i.e. Empty-header; is converted and sent as Empty-header:

>>> Dan
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged
material (including material protected by the solicitor-client or other applicable privileges), or
constitute non-public information. Any use of this information by anyone other than the intended
recipient is prohibited. If you have received this transmission in error, please immediately reply to

Re: simplified progress-bar for dumb terminals

On Mon, 2 Apr 2012, Kamil Dudka wrote:

> dracut developers are asking us to implement a simplified progress bar that 
> would be similar to the output of --progress-bar but compatible with 
> terminals that do not support the '\r' character:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=806426
>
> Does such an enhancement make sense?  Would it be accepted upstream?

I think we can accept such a change.

Maybe such a fix could (try to) detect terminal type and automatically switch 
to the simpler mode?

Anyway, how would it work/look?

--

-- 

  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Re: simplified progress-bar for dumb terminals

On Mon, Apr 02, 2012 at 03:59:09PM +0200, Daniel Stenberg wrote:
> On Mon, 2 Apr 2012, Kamil Dudka wrote:
> >dracut developers are asking us to implement a simplified progress
> >bar that would be similar to the output of --progress-bar but
> >compatible with terminals that do not support the '\r' character:
> >
> >https://bugzilla.redhat.com/show_bug.cgi?id=806426
> >
> >Does such an enhancement make sense?  Would it be accepted upstream?
> 
> I think we can accept such a change.
> 
> Maybe such a fix could (try to) detect terminal type and
> automatically switch to the simpler mode?

That's what the terminfo 'cr' entry is for ("a code to move the cursor to
the left edge of the current row"), but my terminfo lists 'cr=^M' for the
'dumb' terminal as well. It sounds like dumb isn't dumb enough for that
application. Even if curl were to use terminfo, this user would need
to fix his terminal entry.

>>> Dan
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Re: simplified progress-bar for dumb terminals

On Monday 02 April 2012 15:59:09 Daniel Stenberg wrote:
> On Mon, 2 Apr 2012, Kamil Dudka wrote:
> > dracut developers are asking us to implement a simplified progress bar
> > that would be similar to the output of --progress-bar but compatible with
> > terminals that do not support the '\r' character:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=806426
> >
> > Does such an enhancement make sense?  Would it be accepted upstream?
> 
> I think we can accept such a change.
> 
> Maybe such a fix could (try to) detect terminal type and automatically
>  switch to the simpler mode?

I was more thinking of a new option for this.  Nevertheless, detecting term 
capabilities might also be a solution.  The problem is that we need to link
an additional library to access this information.  Or am I missing something?

> Anyway, how would it work/look?

Please have a look at the attached patch.  Any feedback is welcome.

Kamil

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html

Re: simplified progress-bar for dumb terminals

On Wed, Apr 04, 2012 at 02:38:42PM +0200, Kamil Dudka wrote:
> I was more thinking of a new option for this.  Nevertheless, detecting term 
> capabilities might also be a solution.  The problem is that we need to link
> an additional library to access this information.  Or am I missing something?

That's where tgetstr() and tigetstr() are on my Linux box, too.

> Please have a look at the attached patch.  Any feedback is welcome.

> +AC_ARG_WITH(ncurses,
> +AC_HELP_STRING([--with-ncurses],[Enable ncurses support if available]),
> +  [OPT_NCURSES=$withval])
> +
> +if test "x$OPT_NCURSES" != xno; then
> +  if test "x$OPT_NCURSES" = xyes; then
> +    CURL_CHECK_PKGCONFIG(ncurses)
> +    if test "$PKGCONFIG" != "no" ; then
> +      addlib=`$PKGCONFIG --libs ncurses`
> +      addcflags=`$PKGCONFIG --cflags ncurses`

Does curses even come with a pkg-config file?

> +#ifdef USE_NCURSES
> +# include <term.h>
> +#endif

My docs say that both term.h and curses.h need to be included.

> +    if(bar->dummy_term)
> +      fputs(line, bar->out);

Re: simplified progress-bar for dumb terminals

On Wednesday 04 April 2012 16:13:43 Dan Fandrich wrote:
> On Wed, Apr 04, 2012 at 02:38:42PM +0200, Kamil Dudka wrote:
> > I was more thinking of a new option for this.  Nevertheless, detecting
> > term capabilities might also be a solution.  The problem is that we need
> > to link an additional library to access this information.  Or am I
> > missing something?
> 
> That's where tgetstr() and tigetstr() are on my Linux box, too.

Thanks for the review.  I think we first need to reach an agreement that 
detecting term capabilities is really the preferred way to solve the problem.

> > Please have a look at the attached patch.  Any feedback is welcome.
> >
> > +AC_ARG_WITH(ncurses,
> > +AC_HELP_STRING([--with-ncurses],[Enable ncurses support if available]),
> > +  [OPT_NCURSES=$withval])
> > +
> > +if test "x$OPT_NCURSES" != xno; then
> > +  if test "x$OPT_NCURSES" = xyes; then
> > +    CURL_CHECK_PKGCONFIG(ncurses)
> > +    if test "$PKGCONFIG" != "no" ; then
> > +      addlib=`$PKGCONFIG --libs ncurses`
> > +      addcflags=`$PKGCONFIG --cflags ncurses`
> 
> Does curses even come with a pkg-config file?

At least on Fedora and RHEL-6, it does.

> > +#ifdef USE_NCURSES