Add support for CORS #624
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/spee.ch#624
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For the meme creator on .tech, I was linking to images hosted on spee.ch. However, security issues prevented publishing. From MDN:
CORS doesn't allow multiple allowed origins, so the options are:
Access-Control-Allow-Origin: *
and accept security downsides[lbry.tech, lbry.io, lbry.fund, ???]
and returnAccess-Control-Allow-Origin: <allowed_domain>
.@NetOperatorWibby can you confirm this is working as intended for you now?
@kauffj Just remembered this. It is not working as intended.
This is only with linking images from spee.ch to the meme creator on the Playground. The spee.ch images linked on the community page on .tech work. Publishing with images not served from .tech itself creates the above error.
@NetOperatorWibby can you describe the steps to test this?
Alternately, can you verify that it's a problem for all browsers or specific browsers?
@jessopb
/playground
and visit the Publish exampleThis issue affects Firefox and Chrome. The issue persists in production as well.