You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a conversation with Duane Johnson, we discovered that with current versions of Sandstorm, using WILDCARD_HOST=*.example.com means that if you have a blog at blog.example.com, Sandstorm can't tell if blog.example.com is a session subdomain, or if it's a personal publishing domain. It guesses it's a session subdomain, and then refuses to serve the app instance's static content on that domain.
One thing we could do is change the default WILDCARD_HOST to avoid this problem. That wouldn't help existing users, though.
@canadaduane , thanks for running into this bug and for saying so. Because you spoke up on the mailing list a week ago, you brought this to our attention; without that, it might have taken months longer to discover this.
I'm very happy the Sandstorm software is able to provide you with a blog! I hope you'll continue to be vocal in the community. (-:
In a conversation with Duane Johnson, we discovered that with current versions of Sandstorm, using
WILDCARD_HOST=*.example.com
means that if you have a blog atblog.example.com
, Sandstorm can't tell ifblog.example.com
is a session subdomain, or if it's a personal publishing domain. It guesses it's a session subdomain, and then refuses to serve the app instance's static content on that domain.One thing we could do is change the default
WILDCARD_HOST
to avoid this problem. That wouldn't help existing users, though.A different thing we can do is to fix
shell/server/pre-meteor.js
so that if the inbound request doesn't match an active session, then we try the DNS lookup ofsandstorm-www
per https://github.com/sandstorm-io/sandstorm/wiki/Publishing-to-the-user%27s-domainThe text was updated successfully, but these errors were encountered: