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…

Отладка REST API: как включить

Поддержка

pfaffman (Jay Pfaffman) 09.Февраль.2025 13:37:07 2

Вы можете посмотреть файл /var/discourse/shared/standalone/logs/rails/production.log

Тема		Ответов	Просм.
Recipes and tools for debugging the API Development rest-api	4	628	04.04.2022
Cannot get latest posts via json (/posts.json returns 500 error) Bug rest-api	4	1346	15.12.2015
Where does Discourse store and show logs? Self-Hosting reference	8	25146	10.12.2025
Discourse API Reports Support	8	1634	01.11.2017
Can't create GET request route Support	8	1176	10.10.2017

Отладка REST API: как включить

Связанные темы