Data to sign URL encoded

Posted on 2010-01-04
Last Modified: 2013-11-25
I'm going to use a crypto API and in the signature method I read that the data to be signed must be URL encoded. Why is that needed?
Question by:mdoland
    1 Comment
    LVL 33

    Accepted Solution

    It usually isn't - in fact, normally you sign raw binary data, *then* base64 or otherwise armour it if that is needed. Sometimes you sign url encoded data, but that is because the thing you are signing *is* url encoded data, not because its a prerequisite.

    where did you see this requirement?

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Threat Intelligence Starter Resources

    Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

    3 Tips For Quarter Milers: A Sprinter's Understanding of Agile Software Development Two years ago, I wrote a blog entry about Agile software development ( At th…
    Documentation is a big contentious issue in Agile. There is a reason for this. When you start your presentation on Agile you start by going through the 4 statements of agile manifesto (…
    Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
    how to add IIS SMTP to handle application/Scanner relays into office 365.

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now