If I browse to the page myself I can see the output fine, Ive made sure the URLs correct as I opened the link that JSON failed to access. This is working fine for me on another page on the same site but for some reason the console in chrome and firebug say '500 (Internal Server Error)'. #+ client_max_body_size controls the maximum file upload size - this will The page outputs a php array using jsonencode. Given that JSON is often passed as user input, I'd really like it if I could decode strings without worrying about fatal errors and continue with my input validation normally. There is definitely a line for it in /etc/nginx/config/mime.types application/json json īut I can see in chrome dev tools that the type is wrong: I tried putting the absolute URL, the relative URL, and replacing the domain name by the ip address, both local and public in the ajax call, with no success. I tried replacing Input::all() by POST, with no success. If I browse to the page myself I can see the output fine, I've made sure the URL's correct as I opened the link that JSON failed to access. My server is serving my "manifest.json" file as text/plain which means the browser can't read it. If I comment out the jsondecode line, I don't have any error, and the js console correctly logs the data that were sent. The page outputs a php array using jsonencode.
0 kommentar(er)
