You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2015/09/04 16:53:45 UTC
[jira] [Comment Edited] (INFRA-10237) closer.cgi JSON response
missing path_info data
[ https://issues.apache.org/jira/browse/INFRA-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728737#comment-14728737 ]
Sebb edited comment on INFRA-10237 at 9/4/15 2:53 PM:
------------------------------------------------------
Patch to allow for empty strings when building up path_info
[Later] I suspect this won't work - the cgi script redirect probably strips off the trailing path info.
was (Author: sebb@apache.org):
Patch to allow for empty strings when building up path_info
> closer.cgi JSON response missing path_info data
> -----------------------------------------------
>
> Key: INFRA-10237
> URL: https://issues.apache.org/jira/browse/INFRA-10237
> Project: Infrastructure
> Issue Type: Bug
> Components: Mirrors
> Reporter: Chris Beer
> Attachments: INFRA-10237.patch
>
>
> Until a couple days ago, a request like:
> http://www.apache.org/dyn/closer.cgi/lucene/solr/4.2.1/solr-4.2.1.zip?asjson=true
> Contained an element in the JSON response like:
> path_info: "lucene/solr/4.2.1/solr-4.2.1.zip"
> (reconstructed off the top of my head, but something close to that).
> The path_info element is currently blank, which is causing us trouble when programmatically constructing appropriate mirror URLs.
> Will this element be restored, or will consumers have to construct these paths locally?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)