> > Try this and see if it's the HTTP/1.0 stuff. Then if not you can try the > other commits in between (which may need a little massaging, but not a lot): > > git reset --hard 7733c517d7d22ef9b706176b21e1e5e270c65aa5 > git show cc64d59d8132350cadf7adf91857597795eb9090 | sed s/strcasecmp/strcmp/g > | patch -p1 This results in a prompt for the password, so the problem is in those patches, not the intermediate ones. Thanks.
