Hi holgerbrandl,

Generally speaking, all characters do work, in this case since a question mark is a reserved URL parameter character, I'm fairly confident that's what's wrong.

On the API, you'll have to properly escape it no matter what. On the website, I'll make sure to do that. Regardless though, I'm fairly certain our search lib is converting it at the wrong time. I've created a ticket for this here, and will look at it.

Cheers.

Hello Travis,

thank you for your fast reply. I've checked the escaping when using the API, and I still think it's a sever problem: http://api.themoviedb.org/3/search/movie?api_key=APIKEY&query=What+Ever+Happened+to+Baby+Jane%3F&include_adult=false gives and (incorrect) empty result list. The question mark seems correctly encoded as %3F.

Without the escaped question mark 2 results are obtained (which is the expected answer) http://api.themoviedb.org/3/search/movie?api_key=APIKEY&query=What+Ever+Happened+to+Baby+Jane&include_adult=false

Maybe the query parameters are escaped again on the sever side?

Cheers, Holger

Hi Holger,

Yes, that's what I meant. All I was saying was that even when I fix it on the server side, you'll still have to properly escape your search query.

Hi Holger,

I just pushed the fix for this, you can see it working here on the website and you can check this query on the API:

http://api.themoviedb.org/3/search/movie?api_key=###&query=what+ever+happened+to+baby+jane%3F

P.S. The API has that response cached, it will start working in a few hours once the cache has expires.

Cheers.