Encoding problems

[geotinc]

Hello, don't know if it's a real problem but the following code :

produce the following response in postman :

how to have the real key like "Test" and "accessToken" ?

Thanks for helping

[The-EDev]

Like I said in the other issue, this has never happened, could you please provide more information? do the json examples work fine?

[geotinc]

I try the example code :

And I have the same problem :

[The-EDev]

Used the exact same code as you, got this:

Can you tell me what OS you're running, what compiler version, what Crow version, etc...

[geotinc]

It seems that it is an UT8 error :
116 101 115 116 in hexadecimal is :
74 65 73 74 = "test"

My os is :

I build with Visual Studio 2019 :

and the crow version has been installed with vcpkg :

Hope it help.

Thanks a lot.

[The-EDev]

Can you check the URL in your browser instead of postman? This way we can tell whether it's postman or Crow that's giving the problem

[geotinc]

Same in problem in chrome and firefox :

[The-EDev]

hmmm, I'll look into why it's doing that

Update: Even when running Windows 10, I can't seem to recreate the problem..

[geotinc]

For information, if I return directly a string value without instanciate a

It works, do you think other include in my project can alter the rendering of WVVALUE ?

[The-EDev]

it is possible, I don't know what else you're including or what compile settings you have, also it might be best to use this format:
```
Paste Code Here
```
instead of using pictures.

[geotinc]

We have found the problem in json.h file in method
inline void escape(const std::string& str, std::string& ret)

We have replace :
for(unsigned char c:str)

by
for(auto c:str)

And it's work.

Any idea to fix the problem at project level without change libraries code ?

[The-EDev]

This is weird.. The code currently in json.h is for (auto c:str), did you mean change that to for(unsigned char c:str) or are you using an old version of Crow?

[The-EDev]

Oh my god, I'm so so sorry. This issue is a duplicate of #195 and has been fixed on master in #196. I don't know how it slipped past me or why I didn't add it in a new hotfix to 0.3. I'm sorry again.