-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a relative/local WebContext Path argument #25
Comments
Just made all URLs relative in the web UI (for API calls and static content), means you can have a single MailHog instance proxied from different endpoints if you need to (or, continue to use the real MailHog UI as well as the proxied one). I used nginx to test it which gave me some issues with the event stream - switched off proxy buffering and it worked. Thought I'd mention it in case you get the same with Apache. |
Sorry for giving feedback too late, but this doesn't seem to work,
For http://10.100.160.27/mailhog and
|
Just a +1 to say that I'm also trying to proxy through Apache, and have the same issue as oers with the latest version of MailHog. |
@ian-kent could you please reopen this issue? Or should I create a new one? |
I confirm the problem, any solution out there ? |
I am trying to build a solution for this in https://github.com/oers/MailHog-UI. |
Closing this as I think it's been fixed by @oers contributions |
I'm trying to proxy from sibling docker container:
with service "web" providing proxy:
but all I get on http://web/mail is: I am happy about every hint... |
I tried to use Mailhog together with an apache-proxy.
Mailhog tries to resolve all resource absolute to the host:
http://localhost/images/hog.png
I think mailhog needs an optional webcontext argument like -webcontext mailhog, which will then search all resources under /mailhog/.. instead of /
The text was updated successfully, but these errors were encountered: