http - Why is command line computed base64 string different than curl computed base64 string? -


is actually confused - it seems to be done with a single character placement at the end or possible with the basic digest Padding Therefore, if I execute it, you can see the product of base 64 encode:

  echo 'host@mail.com: password' | Now, if I request curl:  
  curl-v-yo host@mail.com: https: password: https: // https: //  

// aG9zdEBtYWlsLmNvbTpwYXNzd29yZA ==

You will notice that the base 64 strings are not the same..what is it? Base64 command line one is actually wrong - if you change into the option, then it fails. SO - Does basic Python really not use a base64 string?

More thoughts?

EDIT: So, this was the last new line echo: -n indexed new lines do not output

thanks!

  & gt; & Gt; & Gt; 'AG 9zdEBtYWlsLmNvbTpwYXNzd29yZA =='. Decode ('base64') 'host@mail.com: Password' & gt; & Gt; & Gt; 'AG9zdEBtYWlsLmNvbTpwYXNzd29yZAo ='. Decode ('base64') 'host@mail.com: password \ n'  

Try echo -n instead.


Comments

Popular posts from this blog

asp.net - Change the driver in the connection string to a data source in VB.Net -

Getting started consuming web services in a Ruby on Rails 3 application -

objective c - iPhone and it's wireless area -