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
FRL-licensed applications that don't use a proxy in their license file send requests to the license server with a leading // in their path (e.g., https://lcs-cops.adobe.io//asnp/frl_connected/values/v2). But these requests are rejected by the adlu-proxy with 405 Method Not Allowed errors. The proxy should be accepting these calls.
First noticed in release v1.0.0-alpha.1.
The text was updated successfully, but these errors were encountered:
This rejection was due to strict path parsing in the underlying warp framework. I have submitted a PR to fix this issue and am using the patched framework in release 1.0.0-alpha.2 (commit 2ae7328).
FRL-licensed applications that don't use a proxy in their license file send requests to the license server with a leading // in their path (e.g.,
https://lcs-cops.adobe.io//asnp/frl_connected/values/v2
). But these requests are rejected by the adlu-proxy with405 Method Not Allowed
errors. The proxy should be accepting these calls.First noticed in release
v1.0.0-alpha.1
.The text was updated successfully, but these errors were encountered: