Did anyone notice when storing files as #/NAME get broken?

[Elan Ruusamäe]

On 05.12.2016 22:38, Jakub Bogusz wrote:
> On Sun, Dec 04, 2016 at 11:27:48PM +0200, Elan Ruusamäe wrote:
>> On 04.12.2016 23:23, Elan Ruusamäe wrote:
>>>
>>> i can't find any match as of now
>>>
>>> $ grep -rF Source ~/all-specs> ~/spec-sources.txt
>>> $ cat ~/spec-sources.txt|grep -E '^(Source|Patch).*#'
>> not sure where my grep went wrong. here's better one with some results.
>> and they can be fixed with changing '#/' to '?/' or '&/'
> Unfortunately it's not the same - with ?/ and &/ the additional part is
> sent to the server and, depending on server software and configuration,
> may cause the download request to be refused.

yes. it is not identical, but usually remote servers just ignore the 
unknown HTTP GET parameters.

variations can include:

&_=/filename-version.tar.gz

in case they fail with empty "key" in GET parameter.



-- 
glen