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 (instead of trying to find it in the log). Thanks!

REST API Debugging – Wie man es aktiviert

Produktunterstützung

pfaffman (Jay Pfaffman) 9. Februar 2025 um 13:37 2

Sie können sich die Datei /var/discourse/shared/standalone/logs/rails/production.log ansehen.

Thema		Antworten	Aufrufe
Recipes and tools for debugging the API Development rest-api	4	667	4. April 2022
Cannot get latest posts via json (/posts.json returns 500 error) Bug rest-api	4	1397	15. Dezember 2015
Where does Discourse store and show logs? Self-Hosting reference	8	25593	10. Dezember 2025
Discourse API Reports Product Support	8	1739	1. November 2017
Can't create GET request route Product Support	8	1250	10. Oktober 2017

REST API Debugging – Wie man es aktiviert

Verwandte Themen