artifactUrl having some extra characters in OCI environment #179
Replies: 1 comment 5 replies
-
Bro, this is happening due to viewer's js trying to fetch latest file out, thinking backend as CDN. Currently oci compact object storage api do not support to handle and ignore invalid url query strings. On production, we use a CDN to front compact object storage. And we have added a rule at CDN to drop any query strings to avoid that. For dev, What I have done is that using my OCI free tier instance (0 cost) as a Nginx instance to drop unwanted query string from the url. So that oci compact store api doesn't throw errors. Here is my sample http config (just run certbot to generate new ssl and auto set this to https) Hope this helps :-) server {
} |
Beta Was this translation helpful? Give feedback.
-
@ddevadat
We observed In OCI DEV, we noticed that after uploading a PDF, there were additional keys such as
?16\
or?32\
in the URL during playback. We encountered a similar issue in the production environment. Do you happen to recall the resolution we implemented for this at that time? If so, could you share the details or any insights that might help us address the current occurrence of the same issue?@gandham-santhosh @mohitga @santhosh-tg @ashokreddy1208
Beta Was this translation helpful? Give feedback.
All reactions