search

suganoo / s3fs

Automatically exported from code.google.com/p/s3fs
0 stars 0 forks source link

Unable to use https on r191 and above #85

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install s3fs 191
2. Connect as usual using the url parameter to make an https connection
3. Do an ls on the new mount

What is the expected output? What do you see instead?
A list of files. Input/output error

What version of the product are you using? On what operating system?
r191 I'm using ubuntu 9.10 and libcurl 7.19.5 I get the same issue on ubuntu 
9.04 with libcurl 
7.18.2

Please provide any additional information below.
r190 and below work fine.

Original issue reported on code.google.com by rowan%wo...@gtempaccount.com on 28 Mar 2010 at 8:03

GoogleCodeExporter commented 8 years ago 
I honestly thought I was going insane when I couldn't get https to work.

Original comment by g1.gilwong@gmail.com on 30 Mar 2010 at 5:39

GoogleCodeExporter commented 8 years ago 
Nah it's a bug in line 1714.  Author assumes the URL should be clipped by 7
characters to get past the "http://" part.  But when you're using SSL, it needs 
to be
8 characters!

Original comment by f3r...@gmail.com on 25 Apr 2010 at 2:49

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Attaching a patch that fixes this.

Original comment by f3r...@gmail.com on 25 Apr 2010 at 3:02

Attachments:

GoogleCodeExporter commented 8 years ago 
F3rrix, you're a champion.  Thanks for figuring this one out!

Original comment by seanca...@gmail.com on 13 Jul 2010 at 4:42

GoogleCodeExporter commented 8 years ago 
Issue 55 has been merged into this issue.

Original comment by dmoore4...@gmail.com on 19 Oct 2010 at 1:47

GoogleCodeExporter commented 8 years ago 
Merged issue #55 with this issue

Incorporating supplied patch.

Original comment by dmoore4...@gmail.com on 19 Oct 2010 at 1:54

GoogleCodeExporter commented 8 years ago 
Duplicated issue and confirmed fix.  Committed revision 202.

Original comment by dmoore4...@gmail.com on 19 Oct 2010 at 2:06