Skip to content

Provide a relative/local WebContext Path argument #25

@oers

Description

@oers

I tried to use Mailhog together with an apache-proxy.

ProxyPass /mailhog http://localhost:8025/
ProxyPassReverse /mailhog http://localhost:8025/

Mailhog tries to resolve all resource absolute to the host:

http://localhost/images/hog.png

image

I think mailhog needs an optional webcontext argument like -webcontext mailhog, which will then search all resources under /mailhog/.. instead of /

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions