Hi Tim,
On Thu, Apr 26, 2018 at 05:33:09PM +0200, Tim Düsterhus wrote:
> Hi
>
> I have got a frontend in mode http that sets various headers
> unconditionally:
>
> > http-response set-headerExpect-CT
> > "max-age=3600;
Hi Andrew,
On Thu, Apr 26, 2018 at 10:06:00PM +0100, Andrew Smalley wrote:
> Hello Haproxy mailing list
>
> I have been looking at caching technology and have found this
>
> https://github.com/jiangwenyuan/nuster/
>
> It claims to be a v1.7 / v1.8 branch fully compatible with haproxy
> and
Hello Louis,
On Thu, Apr 26, 2018 at 02:07:50PM +0200, Louis Chanouha wrote:
> Hello,
>
> I set a global http-reuse safe.
>
> HAProxy displays a warning for http-reuse and send-proxy combinaison on TCP
> mode backends, but http-reuse is active only on HTTP mode backends.
>
> [WARNING]
Hi Tim,
On Fri, Apr 27, 2018 at 09:18:44PM +0200, Tim Duesterhus wrote:
> Tim Duesterhus (2):
> MINOR: sample: Add strcmp sample converter
> MINOR: http: Add support for 421 Misdirected Request
Both patches applied, thanks very much!
Willy
On Fri, Apr 27, 2018 at 08:58:52PM -0600, Ben Draut wrote:
> > > newnameserver->addr = *sk;
> > > }
> > > + else if (strcmp(args[0], "parse-resolv-conf") == 0) {
> >
> > I think you should register a config keyword and parse this in its own
> > function if at all possible,
On Sat, Apr 28, 2018 at 10:01:42AM +0800, aogooc xu wrote:
> thanks, problems have been tested on multiple nodes, upgrade to version 1.7
> without this problem.
OK. It would have been nice to know if 1.6.14 had fixed the issue as well,
as it contains a large number of fixes on top of the version
>
> > I also opted to just use the nameserver's address as its name in the
> > resolvers section, as I thought that would have the highest probability
> of
> > avoiding name conflicts with other configured nameservers. Again I'm open
> > to feedback though.
>
> I think you're right at this point.
thanks, problems have been tested on multiple nodes, upgrade to version 1.7
without this problem.
This may be related to the large number of data added using socket maps,
this is a small probability event.
Hi Thierry,
Op 27-4-2018 om 1:54 schreef PiBa-NL:
Hi Thierry,
Op 26-4-2018 om 12:25 schreef thierry.fourn...@arpalert.org:
Your trace shows a corrupted tree. Maybe it is due to the freebsd
architecture and the corruption is no reproductible on Linux ? I do
not have
freebsd for testing.
Willy,
Am 27.04.2018 um 06:39 schrieb Willy Tarreau:
> I'd proceed differently I think. Just like we do have arithmetic operators
> support variables as arguments, we could have string operators like strcmp()
> which would support a variable as well. Then you could simply put your SNI
> into a
This converter supplements the existing string matching by allowing
strings to be converted to a variable.
Example usage:
http-request set-var(txn.host) hdr(host)
# Check whether the client is attempting domain fronting.
acl ssl_sni_http_host_match ssl_fc_sni,strcmp(txn.host) eq 0
---
This makes haproxy aware of HTTP 421 Misdirected Request, which
is defined in RFC 7540, section 9.1.2.
---
include/types/proto_http.h | 1 +
src/proto_http.c | 11 +++
2 files changed, 12 insertions(+)
diff --git a/include/types/proto_http.h b/include/types/proto_http.h
index
Curl thinks it's being set:
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Set-Cookie: JSESSIONID=7B26C0CAABC706C1942ACF4187FD0608; Path=/path;
HttpOnly
< P3P: CP='IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND
CNT TST'
< Cache-Control: no-store
< Pragma: no-cache
< Expires: -1
Interesting - the vendor didn't notify us about such a change. I'll have
to investigate.
Simon
On 27/04/18 10:59, Maximilian Boehm wrote:
Hi,
Sessions are managed on haproxy with a stick table which stores a JSESSIONID
Just to make sure: Are you sure this application still uses JSESSIONID
N¬Æ§Kó0K"wë,j
Qv /vç<ïÀ¸è?Cӽ¯5à-S¢©®r~æ[±¢¸!jèÇ'è®h¥»++ç-bèiÖÚ©Üx²)àêZ橦Xjب6xZâÛ°)¯m5óOy÷MþÓM4
íz{Kjx.jx1¢{^Ôò¥ë^Æß騧r«±ë
Hi,
We are using haproxy to load balance a vendor application across three
servers. This has been very successful, but recently the vendor has
released a new interface which is a single page AngularJS application,
and since we went live on Tuesday we have been having problems with
premature
16 matches
Mail list logo