Sébastien Huss

There's https://github.com/reinderien/xcal that does a better job tough

Some browser (like chrome) couldnt care less about the content-type (probably doing some mime magic stuff). But some are expecting them (like firefox) and might even whine in some context...

Interrupting a server while the server was managing a request (having a connected client) force the port to be in FIN_WAIT_2 state for the duration of the TCP timeout so...

if you've used [ctrl]-[z], there's 2 options : 1) type "fg" or "bg" to resume the process (in foreground or background) 2) "kill -9 %1" to actually kill the process...

@314159 thanks for for the correction ;) @EChu16 I never had the issue myself (and I'm using this for over 6months). It shouldnt happen imho

Your doing something wrong then. see http://stackoverflow.com/questions/9254891/what-does-content-type-application-json-charset-utf-8-really-mean. All JSON should be Unicode usually UTF8. It look like your JSON library does not conform to the norm. Your client does indeed...

Sorry, I've explain myself wrong it seems. Let's try to clarify and dig into your issue. Every process have a default charset. That default depends on the actual OS and...

I know a thing or 2 about charset because of my other (day-time) life (see my profil pic). I actually never had the issue while coding so take my words...

I would just suggest to be carefull when using "Access-Control-Allow-Origin:*". There's no point of using it here, this suggest you've generalised its usage and this sound like a bad idea.

Add this to the CMakeList.txt : ``` if ("${CMAKE_CXX_COMPILER_ID}" STREQUAL "Clang") set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -ftemplate-depth=1024") endif() ```