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
If a query is added manually after an encrypted url it should still work fine. However, if the encrypted url already has queries, and the added queries mention the same variable, Surveyor should use the encrypted version.
So, a url like: /e/asdlfjasdf/?WorkerId=Mark
Would work and pass WorkerId on to Surveyor.
However, if a url like: /s/?URL=google.com& WorkerId =Mark was encrypted to /e/123abc, then /e/123abc/?WorkerId=Duncan&Day=Tuesday then Surveyor would get {WorkerId: "Mark", Day: "Tuesday"} and we would just ignore the repeated WorkerId value.
The text was updated successfully, but these errors were encountered:
If a query is added manually after an encrypted url it should still work fine. However, if the encrypted url already has queries, and the added queries mention the same variable, Surveyor should use the encrypted version.
So, a url like:
/e/asdlfjasdf/?WorkerId=Mark
Would work and pass
WorkerId
on to Surveyor.However, if a url like:
/s/?URL=google.com& WorkerId =Mark
was encrypted to/e/123abc
, then/e/123abc/?WorkerId=Duncan&Day=Tuesday
then Surveyor would get{WorkerId: "Mark", Day: "Tuesday"}
and we would just ignore the repeatedWorkerId
value.The text was updated successfully, but these errors were encountered: