Open iamstuba opened 1 month ago
Were you able to find a solution? (It's happening to me as well)
Nope. Haven't ever written a line of Ruby, so don't really know how/where the headers are set. I'd hope/think that for anyone more familiar with Ruby and/or MailCatcher this'd be quite an easy fix.
Same issue when installed via Homebrew for version 0.10.0
@joshualip-plaudit @kilis, my current workaround is to just go to http://127.0.0.1:1080/messages/{X}.html
where {X}
is the id of the message I want to see. Not optimal, but at least I can work this way.
Wasn't able to install version 0.9.0
of MailCatcher via Homebrew for some reason.
Hm, this is a weird one. And I can't replicate it -- for me they resolve with the correct content type:
including in Chrome:
mailcatcher --foreground
Starting MailCatcher v0.10.0
==> smtp://127.0.0.1:1025
==> http://127.0.0.1:1080
curl -I http://localhost:1080/assets/mailcatcher.js
HTTP/1.1 404 Not Found
X-Cascade: pass
Content-Type: text/html;charset=utf-8
Content-Length: 145
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Connection: keep-alive
Server: thin
Seems like my initial report was incorrect and the assets
folder isn't even exposed. I've installed MailCatcher through Homebrew.
I've installed MailCatcher through Homebrew.
Ah, interesting. Through the tap? That hasn’t been updated in a very long time.
Oh, there’s an official formula now!
but it’s missing the step that compiles assets. That’s the issue.
Environment:
OS: macOS Sonoma 14.4.1 Ruby: 3.3.2 MailCatcher: 0.10.0 Browser: Google Chrome (125.0.6422.114) and Mozilla Firefox (126.0.1)
The
.js
and.css
files from/assets
are resolving with an incorrectcontent-type
oftext/html
, which prevents browsers from executing them.This issue was not present in the
0.9.0
version of MailCatcher.