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…

Debugging REST API - come abilitare

Supporto

pfaffman (Jay Pfaffman) 9 Febbraio 2025, 1:37pm 2

Puoi controllare /var/discourse/shared/standalone/logs/rails/production.log

Argomento		Risposte	Visualizzazioni
Recipes and tools for debugging the API Development rest-api	4	617	Aprile 4, 2022
Cannot get latest posts via json (/posts.json returns 500 error) Bug rest-api	4	1337	Dicembre 15, 2015
Where does Discourse store and show logs? Self-Hosting reference	8	25066	Dicembre 10, 2025
Discourse API Reports Support	8	1616	Novembre 1, 2017
Can't create GET request route Support	8	1168	Ottobre 10, 2017

Debugging REST API - come abilitare

Argomenti correlati