-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
load-frontend-fits-file-uri #708
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #708 +/- ##
==========================================
+ Coverage 62.33% 62.40% +0.07%
==========================================
Files 50 50
Lines 8982 9002 +20
==========================================
+ Hits 5599 5618 +19
- Misses 3383 3384 +1 ☔ View full report in Codecov by Sentry. |
So the difference from the existing file upload endpoint is that this basically acts as middleware that appends required headers, but doesn't persist the file itself? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, this approach will work as long as dispatcher and frontend have the same Origin (i.e. served on the same domain. Which is the case in our deployments, the dispatcher is proxied through frontend's webserver at /dispatch-data endpoint.)
So there is no need to set any additional header.
Yes and if it were to change it would be easy to check the origin against a list of authorized origins and set the origin in the header response if there's a match |
No description provided.