All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [hail patch 1/1] Make host, url, orig_path dynamic
Date: Tue, 20 Jul 2010 16:34:19 -0400	[thread overview]
Message-ID: <4C46084B.8010104@garzik.org> (raw)
In-Reply-To: <20100720141645.3dc01964@lembas.zaitcev.lan>

On 07/20/2010 04:16 PM, Pete Zaitcev wrote:
> Some of my performance tests for tabled hit truncation again:
>
>   [zaitcev@hitlain tests]$ ./poke5 -v -h niphredil.zaitcev.lan -u auser
>    -p apass -b test -o -k testkey-hitlain/73b84a11e6d83c65e45853338d646042
>    -f testdir/73b84a11e6d83c65e45853338d646042
>   * About to connect() to niphredil.zaitcev.lan port 80 (#0)
>   *   Trying fec0::1:219:b9ff:fe58:7ad6... * TCP_NODELAY set
>   * connected
>   * Connected to niphredil.zaitcev.lan (fec0::1:219:b9ff:fe59:7ad6) port 80 (#0)
>   >  PUT /test/testkey-hitlain/73b84a11e6d83c65e45853338d HTTP/1.1
>   Accept: */*
>   Host: niphredil.zaitcev.lan
>   Date: Tue, 20 Jul 2010 01:07:33 +0000
>   Authorization: AWS testuser:RefcbVYgr2m9KTRxOrCfr4zzfPE=
>   Content-Length: 214745088
>   Expect: 100-continue
>
>   * The requested URL returned error: 403
>
> As you can see, the path in PUT is truncated, and this causes 403
> since it's included into a hash.
>
> The patch addresses this issue and a bunch of other fixed-size
> strings before we hit that.
>
> Signed-off-by: Pete Zaitcev<zaitcev@redhat.com>
>
> ---
>   lib/hstor.c |  147 +++++++++++++++++++++++++++++++++++---------------
>   1 file changed, 104 insertions(+), 43 deletions(-)

applied

  reply	other threads:[~2010-07-20 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 20:16 [hail patch 1/1] Make host, url, orig_path dynamic Pete Zaitcev
2010-07-20 20:34 ` Jeff Garzik [this message]
2010-07-29 17:41   ` Pete Zaitcev
2010-07-29 17:56     ` Jeff Garzik

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=4C46084B.8010104@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.org \
    --cc=zaitcev@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.