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

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

話題		回覆	觀看
Recipes and tools for debugging the API Development rest-api	4	653	2022年四月4日
Cannot get latest posts via json (/posts.json returns 500 error) Bug rest-api	4	1364	2015年十二月15日
Where does Discourse store and show logs? Self-Hosting reference	8	25444	2025年十二月10日
Discourse API Reports Support	8	1669	2017年十一月1日
Can't create GET request route Support	8	1210	2017年十月10日

REST API 调试 - 如何启用

相關主題