From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin package search and cygcheck -p urlencoding still broken on new web server
Date: Thu, 16 Jul 2020 14:22:01 -0600 [thread overview]
Message-ID: <2d1e4b1d-8680-34bd-d630-380e1b125d1a@SystematicSw.ab.ca> (raw)
In-Reply-To: <acc98a4e-68e5-d70e-6271-50c6f0dfb364@dronecode.org.uk>
On 2020-07-16 07:42, Jon Turney wrote:
> On 16/07/2020 08:44, Marco Atzeri via Cygwin wrote:
>> On 16.07.2020 06:25, Brian Inglis wrote:
>>> On 2020-07-15 14:13, Marco Atzeri via Cygwin wrote:
> So it seems the urlencode is correct, but the urldecode isn't working.
>
> I've applied a one-character change which appears to fix things.
>> the git logs says that only Frank and Jon have recently worked on
>>
>> cgi-bin2/package-grep.cgi
>>
>> I would like to double check any possible modification before proposing a
>> patch to change the web server...
> This was actually fairly easy to reproduce locally, once I realized what was
> going on:
>
> $ export url="libssh%2Flibssh.h" ; printf '%b' "${url//%/\x}"
> libsshx2Flibssh.h
>
> $ export url="libssh%2Flibssh.h" ; printf '%b' "${ur//%/\\x}"
> libssh/libssh.h
Doh! Good catch! Been an annoyance for months.
I didn't realize cgi-bin scripts were visible under cygwin-htdocs/cgi-bin2.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2020-07-16 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 20:13 Broken search on webserver Marco Atzeri
2020-07-16 4:25 ` Cygwin package search and cygcheck -p urlencoding still broken on new web server Brian Inglis
2020-07-16 7:44 ` Marco Atzeri
2020-07-16 13:42 ` Jon Turney
2020-07-16 18:48 ` Marco Atzeri
2020-07-16 20:22 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d1e4b1d-8680-34bd-d630-380e1b125d1a@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).