enhanced the getGraphiteURLKey function to replace additional characters

[EikeDawid]

Fixes #651

I run into some issues with certain characters on URI that where clashing with graphite functionality or caused parsing issues for grafana when trying to retrieve data from graphite

The characters are:

• pipe (|)
• comma (,)
• plus (+)

... they are replaced by a _ (as the others are)

[soulgalore]

Hello @EikeDawid , I've changed so we use pipe char instead of %7C , I think the URL should already be decoded or have you seen that it don't work in your case?

Best
Peter

[EikeDawid]

@soulgalore: I had to do it cause url.parse(theUrl); returns the | encoded on my node version.

However i just checked the build (on travis) and i see the encoded version is failing on node 0.10, while the un-encoded fails on 0.12.

So that means that url.parse(theUrl); behaves differently on both.

That's a bit of a bummer - there are some other changes too:
nodejs/node-v0.x-archive#8332

Sorry, that i did not check on an older node version ....

I think the fastest way to make it work consistently would be to add both versions (encode and unencoded). Shall i send another pull request with that?

[soulgalore]

@EikeDawid I'll fix it now, that's no problem. When I checked your test, I didn't see you added two different tests for pipe, that's nice. I'll check it in now and see if it works :)