[GH-ISSUE #147] MP_WEBROOT is ignored in the API-Documentation #99

New issue

Closed

opened 2026-03-15 12:32:31 +03:00 by kerem · 4 comments

kerem commented

2026-03-15 12:32:31 +03:00

Owner

Originally created by @christian-scheible on GitHub (Jul 25, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/147

I have set MP_WEBROOT to mailcatcher. However when I am visiting http://localhost/mailcatcher/api/v1/ the documentation shows:

API Server http://localhost

and if I try to test a request using the TRY button, the request fails as it doesn't append mailcatcher to the request.

So it tries http://localhost/api/v1/info instead of http://localhost/mailcatcher/api/v1/info

Originally created by @christian-scheible on GitHub (Jul 25, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/147 I have set **MP_WEBROOT** to _mailcatcher_. However when I am visiting http://localhost/mailcatcher/api/v1/ the documentation shows: **API Server http://localhost** and if I try to test a request using the **TRY** button, the request fails as it doesn't append mailcatcher to the request. So it tries `http://localhost/api/v1/info` instead of `http://localhost/mailcatcher/api/v1/info`

kerem

2026-03-15 12:32:31 +03:00

closed this issue
added the
documentation

bug
labels

kerem commented

2026-03-15 12:32:47 +03:00

Author

Owner

@axllent commented on GitHub (Jul 25, 2023):

You are absolutely right - currently the swagger config does not take the current webroot into consideration. I'll need to think of a solution for this as the swagger.json spec file for the API (used in the docs you are referring to) is embedded in the application, and not dynamically generated based on startup arguments.

@axllent commented on GitHub (Jul 25, 2023): You are absolutely right - currently the swagger config does not take the current webroot into consideration. I'll need to think of a solution for this as the `swagger.json` spec file for the API (used in the docs you are referring to) is embedded in the application, and not dynamically generated based on startup arguments.

kerem commented

2026-03-15 12:32:52 +03:00

Author

Owner

@christian-scheible commented on GitHub (Jul 25, 2023):

@axllent, that was quick, thank you! It's not a blocker for me, as I am now using Postman to explore the API. However, I believe honoring the environment variable would make it easier for other users.

@christian-scheible commented on GitHub (Jul 25, 2023): @axllent, that was quick, thank you! It's not a blocker for me, as I am now using Postman to explore the API. However, I believe honoring the environment variable would make it easier for other users.

kerem commented

2026-03-15 12:32:57 +03:00

Author

Owner

@axllent commented on GitHub (Jul 30, 2023):

@christian-scheible This should be fixed now in the latest release 🚀 Please feel free to re-open this ticket if it's not working as you expected.

@axllent commented on GitHub (Jul 30, 2023): @christian-scheible This should be fixed now in the latest release :rocket: Please feel free to re-open this ticket if it's not working as you expected.

kerem commented

2026-03-15 12:33:02 +03:00

Author

Owner

@christian-scheible commented on GitHub (Jul 31, 2023):

@axllent Thank you for the quick solution. It is now working as expected.

@christian-scheible commented on GitHub (Jul 31, 2023): @axllent Thank you for the quick solution. It is now working as expected.

kerem referenced this issue

2026-03-15 14:19:05 +03:00

[PR #99] [CLOSED] Bump wangyoucao577/go-release-action from 1.37 to 1.38 #441