I was trying to use Udash for a simple project recently.
I used the Udash REST API to call a backend designed using the Flight PHP framework (http://www.flightphp.com).
The backend URLs were database queries which failed to produce the correct result on Chrome Browser v45. On debugging, I found that the URLs called by the REST API (via URLPart or standard query string parameter) had been double-encoded; the spaces " " were turned into "%2520" instead of "%20".
I thought I should use POST, but the Udash documentation isn't very clear on on how to pass POST parameters to the backend API: Is it via @Query or @Body?
So, I ended up manually de-encoding the entity myself.
Hi (To Whom It May Concern):
I was trying to use Udash for a simple project recently.
I used the Udash REST API to call a backend designed using the Flight PHP framework (http://www.flightphp.com).
The backend URLs were database queries which failed to produce the correct result on Chrome Browser v45. On debugging, I found that the URLs called by the REST API (via URLPart or standard query string parameter) had been double-encoded; the spaces " " were turned into "%2520" instead of "%20".
I thought I should use POST, but the Udash documentation isn't very clear on on how to pass POST parameters to the backend API: Is it via @Query or @Body?
So, I ended up manually de-encoding the entity myself.
Could this bug be patched?