Re: help w/ md5sum PUT

Re: help w/ md5sum PUT

[David Birdsong]

[resending to the correct cmogstored list]

On Tue, Feb 3, 2015 at 3:59 PM, David Birdsong <david.birdsong@gmail.com>
wrote:

> Hi Eric, I'm troubleshooting my client that's PUTing to cmogstored and
> getting 400 response codes.
>
> If I supply a header:
> Content-MD5: MJH_pL-pTjsfQV4PiYDLFA==
>
> cmogstored returns a 400.
>
> If I don't set it, I get a 201 and find the fid on disk and see that its
> md5 sum (hex encoded) is: 3091ffa4bfa94e3b1f415e0f8980cb14
>
>
> python -c "print 'MJH_pL-pTjsfQV4PiYDLFA=='.decode('base64').encode('hex')"
>
> 3091e92e94e3b1f415e0f8980cb140
>
> Got any tips as to how to get cmogstored to allow this MD5?
>
> I built cmogstored built at version 1.4.1
>

Re: help w/ md5sum PUT

[Eric Wong]

David Birdsong <david.birdsong@gmail.com> wrote:
> On Tue, Feb 3, 2015 at 3:59 PM, David Birdsong <david.birdsong@gmail.com>
> wrote:
> 
> > Hi Eric, I'm troubleshooting my client that's PUTing to cmogstored and
> > getting 400 response codes.
> >
> > If I supply a header:
> > Content-MD5: MJH_pL-pTjsfQV4PiYDLFA==

How are you generating that base64?

I could be wrong, but it the '_' (underscore) is not a part of the
normal set of characters used by base64.  Perhaps you're using a base64
variant? (there's one URL-friendly variant, at least)

It doesn't look like the gnulib base64 module (which cmogstored uses)
handles underscore... (warning: I'm sleep deprived and haven't touched
a computer in a few days, so maybe I'm missing something, too)

Re: help w/ md5sum PUT

[David Birdsong]

On Tue, Feb 3, 2015 at 4:20 PM, Eric Wong <e@80x24.org> wrote:

> David Birdsong <david.birdsong@gmail.com> wrote:
> > On Tue, Feb 3, 2015 at 3:59 PM, David Birdsong <david.birdsong@gmail.com
> >
> > wrote:
> >
> > > Hi Eric, I'm troubleshooting my client that's PUTing to cmogstored and
> > > getting 400 response codes.
> > >
> > > If I supply a header:
> > > Content-MD5: MJH_pL-pTjsfQV4PiYDLFA==
>
> How are you generating that base64?
>
> I could be wrong, but it the '_' (underscore) is not a part of the
> normal set of characters used by base64.  Perhaps you're using a base64
> variant? (there's one URL-friendly variant, at least)
>
> It doesn't look like the gnulib base64 module (which cmogstored uses)
> handles underscore... (warning: I'm sleep deprived and haven't touched
> a computer in a few days, so maybe I'm missing something, too)
>

It's from Golang's base64 package:
return base64.URLEncoding.EncodeToString(m.checksum.Sum(nil))

...but yeah, here's python's re-encoding:
>>> base64.urlsafe_b64encode(
base64.decodestring('MJH_pL-pTjsfQV4PiYDLFA=='))

'MJHpLpTjsfQV4PiYDLFA'


I'll try playing around with other Go encoding methods.

Re: help w/ md5sum PUT

[David Birdsong]

On Tue, Feb 3, 2015 at 4:24 PM, David Birdsong <david.birdsong@gmail.com>
wrote:

>
>
> On Tue, Feb 3, 2015 at 4:20 PM, Eric Wong <e@80x24.org> wrote:
>
>> David Birdsong <david.birdsong@gmail.com> wrote:
>> > On Tue, Feb 3, 2015 at 3:59 PM, David Birdsong <
>> david.birdsong@gmail.com>
>> > wrote:
>> >
>> > > Hi Eric, I'm troubleshooting my client that's PUTing to cmogstored and
>> > > getting 400 response codes.
>> > >
>> > > If I supply a header:
>> > > Content-MD5: MJH_pL-pTjsfQV4PiYDLFA==
>>
>> How are you generating that base64?
>>
>> I could be wrong, but it the '_' (underscore) is not a part of the
>> normal set of characters used by base64.  Perhaps you're using a base64
>> variant? (there's one URL-friendly variant, at least)
>>
>> It doesn't look like the gnulib base64 module (which cmogstored uses)
>> handles underscore... (warning: I'm sleep deprived and haven't touched
>> a computer in a few days, so maybe I'm missing something, too)
>>
>
> It's from Golang's base64 package:
> return base64.URLEncoding.EncodeToString(m.checksum.Sum(nil))
>
> ...but yeah, here's python's re-encoding:
> >>> base64.urlsafe_b64encode(
> base64.decodestring('MJH_pL-pTjsfQV4PiYDLFA=='))
>
> 'MJHpLpTjsfQV4PiYDLFA'
>
>
> I'll try playing around with other Go encoding methods.
>

Ok, I swapped in base64.StdEncoding and it worked.
http://golang.org/pkg/encoding/base64/#pkg-index

I expected the base64.URLEncoding to be the way to go.

Case closed.

Thanks!