airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (Jira)" <>
Subject [jira] [Commented] (AIRAVATA-3303) 404 Not Found when forward slash in experiment id
Date Wed, 25 Mar 2020 13:19:00 GMT


Marcus Christie commented on AIRAVATA-3303:

I tried to get encoded forward slashes to work, here's what I had to do:
* enable [AllowEncodedSlashes|]
in Apache virtual host
* in ExperimentViewSet set {{lookup_value_regex = ".*"}}
** also FullExperimentViewSet
** also SharedEntityViewSet

This "works", however it still would fail if there is more than one forward slash consecutively
because Apache collapses multiple consecutive forward slashes into one slash, see

Because of this and because I'd rather not have the Django portal code be dependent on how
the proxying web server is configured, I think it would be better to remove forward slashes
from the experiment ID on the backend.  That should be simple enough but it will require some
data migration to remove forward slashes from existing experiment IDs that contain them.

> 404 Not Found when forward slash in experiment id
> -------------------------------------------------
>                 Key: AIRAVATA-3303
>                 URL:
>             Project: Airavata
>          Issue Type: Improvement
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
> API request to load experiment when id has forward slash results in 404 not found. 
> For example:
> {{%2F}} is the encoded forward slash.
> Apparently even though encoded properly the forward slash being decoded at some point
and considered part of the URL.

This message was sent by Atlassian Jira

View raw message