I’m doing a REST call to /uploads.json, which works fine in postman, but not in the client that I’m writing. Discourse response contains an empty string - probably I’m missing something. Is there another approach to see how an incoming REST call gets processed and why a 400 response is generated?

You can look at /var/discourse/shared/standalone/logs/rails/production.log

I’m using the docker image provided by tiredofit/discourse, and apparently there is no production.log [tiredofit/discourse:3.2.2 08:28:46 ~] $ find / -name production.log [tiredofit/discourse:3.2.2 08:29:02 ~] $ I took another route and used the postman proxy to see what the app is sending (instea…

Depuración de REST API - cómo habilitar

Soporte

pfaffman (Jay Pfaffman) 9 Febrero, 2025 13:37 2

Puedes mirar en /var/discourse/shared/standalone/logs/rails/production.log

Tema		Respuestas	Vistas
Recipes and tools for debugging the API Development rest-api	4	617	4 Abril 2022
Cannot get latest posts via json (/posts.json returns 500 error) Bug rest-api	4	1337	15 Diciembre 2015
Where does Discourse store and show logs? Self-Hosting reference	8	25050	10 Diciembre 2025
Discourse API Reports Support	8	1616	1 Noviembre 2017
Can't create GET request route Support	8	1166	10 Octubre 2017

Depuración de REST API - cómo habilitar

Temas relacionados