Project

General

Profile

Support #18

Create Another Map (was Sandstorm changes grain origin, creating CORS violations (was Create Another Map))

Added by Jay Gischer over 5 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Joanna Winter
Start date:
04/09/2020
Due date:
% Done:

0%

Estimated time:
Spent time:
9.00 h

Description

As discussed in Weds meeting, create a map using the app at Mansia.net so you can give us feedback on UI/UX. Also take note of roughly how much time it takes.

#1

Updated by Jay Gischer over 5 years ago

  • Subject changed from Create another map to Sandstorm changes grain origin, creating CORS violations (was Create Another Map)
  • Status changed from New to In Progress
  • Assignee changed from Joanna Winter to Jay Gischer
  • Priority changed from Normal to High

Ok, so you found a good one. First of all, the instance on Mansia didn't really update properly. Once I killed it and started the new code, I reproduced the problem. I'm getting 403 (Unauthorized) on all images because, at some point, Sandstorm is switching the grain id (they warned me that it was ephemeral!) and this makes the image references a security violation. I'm sure there's a way around this, just have to figure it out.

Reassigning to me until I fix this.

#2

Updated by Jay Gischer over 5 years ago

  • Subject changed from Sandstorm changes grain origin, creating CORS violations (was Create Another Map) to Create Another Map (was Sandstorm changes grain origin, creating CORS violations (was Create Another Map))
  • Assignee changed from Jay Gischer to Joanna Winter
  • Priority changed from High to Normal

Ok, I have found and fixed this problem, and I'm reassigning it back to Joanna. So she can once more try to create a map.

The problem was a CORS violation (403) that happens when the "ephemeral host name" that sandstorm contrives changes. I didn't track it correctly, and when it changed, the browser says, "hey, that content comes from a different host than this webpage comes from and that's insecure!" Which is legit.

But the way I found around this issue is not by being even more careful to track the ephemeral hostname, but by eliminating the host/protocol prefix altogether, which has always been a legitimate form of reference. Sigh. I've had the answer all the time.

#3

Updated by Joanna Winter over 5 years ago

Ok, time spent log double posted. Hit some button wrong.

#4

Updated by Administrator Administrator about 3 years ago

  • Status changed from In Progress to Closed

Joanna has successfully created another map.

Also available in: Atom PDF