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
@jimlears yeah - i think one of the biggest problems is that it would need to return the headers for multiple requests as well.
My current though is I can add an additional parameter that is an array of request objects that you can then access the header information in (should be formatted the same way between server / client). Looks like we could do that in the shared/fetcher.js
what's the best way to get access to the response headers from a REST call with the following conditions?
*this is causing Browserify issues currently and, I hope, there has to be a better/easier way to get at those headers without a lot of custom code.
The text was updated successfully, but these errors were encountered: