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) 2025 年2 月 9 日 13:37 2

您可以查看 /var/discourse/shared/standalone/logs/rails/production.log

话题		回复	浏览量
Recipes and tools for debugging the API Development rest-api	4	617	2022 年4 月 4 日
Cannot get latest posts via json (/posts.json returns 500 error) Bug rest-api	5	1337	2015 年12 月 15 日
Where does Discourse store and show logs? Self-Hosting reference	8	25049	2025 年12 月 10 日
Discourse API Reports Support	9	1616	2024 年6 月 8 日
Can't create GET request route Support	9	1166	2024 年6 月 8 日

REST API 调试 - 如何启用

相关话题