On 4/15/22 06:40, Shawn Heisey wrote:
The 403 is random. While clicking around in my webmail, going to
different folders, I occasionally see a red box that has an error
message pop up, an error message I can't recall at the moment. That's
when the 403 is logged.
I noticed there was another
On 4/15/2022 1:20 AM, Amaury Denoyelle wrote:
Hum this is strange. Do you have a way to reproduce it easily ?
The 403 is random. While clicking around in my webmail, going to
different folders, I occasionally see a red box that has an error
message pop up, an error message I can't recall at
On Thu, Apr 14, 2022 at 07:29:20AM -0600, Shawn Heisey wrote:
> On 4/14/22 03:27, Amaury Denoyelle wrote:
> > So to summary, this option should be activated if you only have browsers
> > as client and the traffic is big enough to saturate haproxy queues.
> > I hope this will clarify your thoughts,
On 4/14/22 03:27, Amaury Denoyelle wrote:
So to summary, this option should be activated if you only have browsers
as client and the traffic is big enough to saturate haproxy queues.
I hope this will clarify your thoughts,
Thanks for that detail. For these setups, I really doubt that there
On Wed, Apr 13, 2022 at 08:16:06AM -0600, Shawn Heisey wrote:
> On 4/13/22 02:42, Amaury Denoyelle wrote:
> > Ok this seems related to 'option abortonclose'. Without this, I do not
> > have a 400 error. Can you confirm me this behavior on your side please ?
>
> If I remove that, it works. I can
On 4/13/22 02:42, Amaury Denoyelle wrote:
Ok this seems related to 'option abortonclose'. Without this, I do not
have a 400 error. Can you confirm me this behavior on your side please ?
If I remove that, it works. I can have my webmail served via http/3 and
login still works, which it
On Wed, Apr 13, 2022 at 10:36:00AM +0200, Amaury Denoyelle wrote:
> On Tue, Apr 12, 2022 at 10:30:05AM -0600, Shawn Heisey wrote:
> > On 4/12/22 09:45, Amaury Denoyelle wrote:
> > > After much analysis of the code, it may be useful to have a run with the
> > > stream traces as well :
> > > $ trace
On Tue, Apr 12, 2022 at 10:30:05AM -0600, Shawn Heisey wrote:
> On 4/12/22 09:45, Amaury Denoyelle wrote:
> > After much analysis of the code, it may be useful to have a run with the
> > stream traces as well :
> > $ trace stream sink buf0; trace stream level developer; trace stream
> > verbosity
On 4/12/22 19:20, Shawn Heisey wrote:
https://paste.elyograg.org/view/bd5df44d
I repeated it, this time issuing the stream traces first, just in case
the order of the trace commands might matter. THat's the sort of thing
that shouldn't matter,
https://paste.elyograg.org/view/22ddec0a
And
On 4/12/22 16:06, Frederic Lecaille wrote:
so this command:
$ echo "trace quic sink buf0; trace quic level developer; trace quic
verbosity clean; trace quic start now; trace qmux sink buf0; trace qmux
level developer; trace qmux verbosity minimal; trace qmux start now;
trace stream sink
On 4/12/22 22:42, Shawn Heisey wrote:
>> Please, you could you double check on your side the "stream" traces are
>> correctly enabled? Also ensure you provide use with traces dumped by
>> haproxy when you validate the PHP form.
>
>
> These are the trace commands that I am sending to the stats
On 4/12/22 14:07, Frederic Lecaille wrote:
Please, you could you double check on your side the "stream" traces are
correctly enabled? Also ensure you provide use with traces dumped by
haproxy when you validate the PHP form.
These are the trace commands that I am sending to the stats socket:
Hello Shawn,
On 4/12/22 18:30, Shawn Heisey wrote:
> On 4/12/22 09:45, Amaury Denoyelle wrote:
>> After much analysis of the code, it may be useful to have a run with the
>> stream traces as well :
>> $ trace stream sink buf0; trace stream level developer; trace stream
>> verbosity clean; trace
On 4/12/22 09:45, Amaury Denoyelle wrote:
After much analysis of the code, it may be useful to have a run with the
stream traces as well :
$ trace stream sink buf0; trace stream level developer; trace stream verbosity
clean; trace stream start now
All 3 traces enabled, this time it should
On Tue, Apr 12, 2022 at 05:26:41PM +0200, Amaury Denoyelle wrote:
> On Tue, Apr 12, 2022 at 08:01:59AM -0600, Shawn Heisey wrote:
> > On 4/12/22 02:22, Amaury Denoyelle wrote:
> > > then you can display the traces with the following command :
> > > $ show events buf0
> > > > For the h3 layer, the
On 4/12/22 08:01, Shawn Heisey wrote:
I didn't do the H3 debug yet, if you still need it after looking at > the traces, let me know. You'll also need to tell me how to make >
those debugs active when I build haproxy.
I figured this out. I put those debug definitions in a DEBUG="stuff"
On Tue, Apr 12, 2022 at 08:01:59AM -0600, Shawn Heisey wrote:
> On 4/12/22 02:22, Amaury Denoyelle wrote:
> > then you can display the traces with the following command :
> > $ show events buf0
> > > For the h3 layer, the trace mechanism is not currently implemented. You
> > should instead
On 4/12/22 02:22, Amaury Denoyelle wrote:
then you can display the traces with the following command :
$ show events buf0
For the h3 layer, the trace mechanism is not currently implemented. You
should instead recompile your haproxy binary with the DEBUG options :
-DDEBUG_H3 -DDEBUG_QPACK
and
On Tue, Apr 12, 2022 at 08:14:25AM +0200, Willy Tarreau wrote:
> Hi Shawn,
> [...]
> On Mon, Apr 11, 2022 at 01:05:21PM -0600, Shawn Heisey wrote:
> > An astute observer will notice that the backend says 81 while the packet
> > capture shows port 82. This is because I changed the port number on
Shawn, I wonder if there a test suite similar to h2check (which is http2
and hpack).
I saw some quic conformance test reported on release notes, but it seem did
not catch POST issue. Should we try to report to them?
On Tue, Apr 12, 2022, 4:45 AM Shawn Heisey wrote:
> On 4/11/2022 4:51 PM,
Hi Shawn,
On Mon, Apr 11, 2022 at 01:05:21PM -0600, Shawn Heisey wrote:
> On 4/11/22 12:16, Shawn Heisey wrote:
> > Two different browsers have the same problem, so I am currently
> > speculating that it's an issue with haproxy or apache. I think I can
> > install nginx without too much trouble
On 4/11/2022 4:51 PM, Shawn Heisey wrote:
I have a more reliable way of reproducing the problem. Finally found
a way to get a version of curl that supports http3. On a machine with
docker and Internet connectivity, run this command:
sudo docker run -it --rm ymuski/curl-http3 curl -v
On 4/11/2022 1:05 PM, Shawn Heisey wrote:
I changed the backend to talk to nginx instead of apache. It still
throws a 400 when the POST is done via http/3. It was an adventure
trying to figure out how to allow POST requests in nginx. The 400
appears to be coming from haproxy. There is
On 4/11/22 12:16, Shawn Heisey wrote:
Two different browsers have the same problem, so I am currently
speculating that it's an issue with haproxy or apache. I think I can
install nginx without too much trouble ... I have almost no experience
with it, so I get to learn something new.
Starting a new thread for this.
I got HTTP/3 working with haproxy. Everything seemed to be going great,
and then I noticed that logins on PHP apps were getting a 400 response
back. At first I thought it might be something in PHP, but I have now
eliminated PHP as the problem. I can
25 matches
Mail list logo
