Re: Proposal: URL API extension, second setter function to allow setting from CURLU object

2023-10-23 Thread Mark Gaiser via curl-library
On Mon, Oct 23, 2023 at 8:57 AM Daniel Stenberg wrote: > On Sun, 22 Oct 2023, Mark Gaiser via curl-library wrote: > > > I get that this is c-code and just the c-way of doing things. Still, it > can > > be simplified a lot, even in c. > > > > I propose a new UR

Proposal: URL API extension, second setter function to allow setting from CURLU object

2023-10-22 Thread Mark Gaiser via curl-library
Hi, This is a slightly more thought out (and scoped down) version of what I said here [1]. In implementing IPFS URL support in curl I had to do many interactions with the URL api. So many that it made me wonder: "can't this be done simpler?" This code essentially needs to compose a new/updated

Re: IPFS, exploring the option for a default header to make gateway behavior explicit?

2023-10-20 Thread Mark Gaiser via curl-library
On Fri, Oct 20, 2023 at 7:25 PM Mark Gaiser wrote: > > > On Fri, Oct 20, 2023 at 6:54 PM Daniel Stenberg wrote: > >> On Fri, 20 Oct 2023, Mark Gaiser via curl-library wrote: >> >> > These are just my thoughts. >> >> > The way IPFS gateway

Re: IPFS, exploring the option for a default header to make gateway behavior explicit?

2023-10-20 Thread Mark Gaiser via curl-library
On Fri, Oct 20, 2023 at 6:54 PM Daniel Stenberg wrote: > On Fri, 20 Oct 2023, Mark Gaiser via curl-library wrote: > > > These are just my thoughts. > > > The way IPFS gateways currently work by default (configurable in its > > settings) is to redirect the path bas

IPFS, exploring the option for a default header to make gateway behavior explicit?

2023-10-20 Thread Mark Gaiser via curl-library
Disclaimer: These are just my thoughts. I don't work for Protocol Labs (company behind IPFS) anymore and am in that sense just an IPFS enthusiastic dev that tries to make it more usable. Hi, An IPFS URL passed to a gateway, like this (safe to try, it's big buck bunny):

Re: Implementing IPFS support in cURL

2022-03-24 Thread Mark Gaiser via curl-library
On Thu, Mar 24, 2022 at 10:09 AM Daniel Stenberg wrote: > On Thu, 24 Mar 2022, Mark Gaiser wrote: > > > I might have been wrong here. My thinking was that "ipfs://" should > be > > handled as: > > protocol: ipfs > > path: cid > > > > But this is a non issue if it's purely handled on the tool

Re: Implementing IPFS support in cURL

2022-03-23 Thread Mark Gaiser via curl-library
On Thu, Mar 24, 2022 at 12:41 AM Daniel Stenberg wrote: > On Wed, 23 Mar 2022, Mark Gaiser via curl-library wrote: > > > - ipfs://QmbGtJg23skhvFmu9mJiePVByhfzu5rwo74MEkVDYAmF5T > > becomes this format: > > - /ipfs/QmbGtJg23skhvFmu9mJiePVByhfzu5rwo74MEkVDYAmF5T > >

Implementing IPFS support in cURL

2022-03-23 Thread Mark Gaiser via curl-library
Hi, For reference see [1] from an attempt that tried to implement it in the library but pulled back. For a very short summary of how an implementation would look like. IPFS [2] data can be accessed through gateways [3]. The intention here is to translate an IPFS url into a http(s) gateway url.