Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FRL activation requests with leading // in their path are rejected by adlu-proxy #1

Closed
clickonetwo opened this issue Sep 2, 2022 · 1 comment
Closed

FRL activation requests with leading // in their path are rejected by adlu-proxy #1

clickonetwo opened this issue Sep 2, 2022 · 1 comment
Assignees
@clickonetwo
Labels
bug Something isn't working

Comments

@clickonetwo
Copy link
Owner

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.
@clickonetwo clickonetwo added the bug Something isn't working label Sep 2, 2022
@clickonetwo clickonetwo self-assigned this Sep 2, 2022
@clickonetwo
Copy link
Owner Author

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@clickonetwo clickonetwo

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@clickonetwo