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
We dont have an easy way to distinguish epivis-originated API requests in our server logs, making it somewhat difficult to measure actual usage of epivis. We could prepend/append to or replace (im not sure right now which choice would be most appropriate) the User-Agent header with something epivis specific, or we could possibly do it via the Origin or Referer headers instead.
Current headers (for me) appear to be something like:
Origin: https://delphi.cmu.edu
Referer: https://delphi.cmu.edu/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
The text was updated successfully, but these errors were encountered:
We dont have an easy way to distinguish epivis-originated API requests in our server logs, making it somewhat difficult to measure actual usage of epivis. We could prepend/append to or replace (im not sure right now which choice would be most appropriate) the
User-Agent
header with something epivis specific, or we could possibly do it via theOrigin
orReferer
headers instead.Current headers (for me) appear to be something like:
The text was updated successfully, but these errors were encountered: