Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 43F47200D5C for ; Fri, 1 Dec 2017 00:51:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 42477160C01; Thu, 30 Nov 2017 23:51:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 99335160C18 for ; Fri, 1 Dec 2017 00:51:04 +0100 (CET) Received: (qmail 27587 invoked by uid 500); 30 Nov 2017 23:51:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 27536 invoked by uid 99); 30 Nov 2017 23:51:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2017 23:51:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 05EAAC5CB8 for ; Thu, 30 Nov 2017 23:51:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.811 X-Spam-Level: X-Spam-Status: No, score=-99.811 tagged_above=-999 required=6.31 tests=[KB_WAM_FROM_NAME_SINGLEWORD=0.2, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 97v0uWLQPWw8 for ; Thu, 30 Nov 2017 23:51:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 448705F65C for ; Thu, 30 Nov 2017 23:51:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 803DBE0EFA for ; Thu, 30 Nov 2017 23:51:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3E48E21066 for ; Thu, 30 Nov 2017 23:51:00 +0000 (UTC) Date: Thu, 30 Nov 2017 23:51:00 +0000 (UTC) From: "Sergey Soldatov (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-19393) HTTP 413 FULL head while accessing HBase UI using SSL. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 30 Nov 2017 23:51:05 -0000 [ https://issues.apache.org/jira/browse/HBASE-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated HBASE-19393: ------------------------------------ Attachment: HBASE-19393.patch Since setHeaderBufferSize is the method of Connector we may apply it to both regular and ssl connectors, so moving it out of createDefaultChannelConnector() which we use for setting SelectChannelConnector and AbstractConnector specific properties. FYI [~elserj] [~apurtell] > HTTP 413 FULL head while accessing HBase UI using SSL. > ------------------------------------------------------- > > Key: HBASE-19393 > URL: https://issues.apache.org/jira/browse/HBASE-19393 > Project: HBase > Issue Type: Bug > Components: UI > Affects Versions: 1.4.0 > Environment: SSL enabled for UI/REST. > Reporter: Sergey Soldatov > Assignee: Sergey Soldatov > Fix For: 1.4.0 > > Attachments: HBASE-19393.patch > > > For REST/UI we are using 64Kb header buffer size instead of the jetty default 6kb (?). But it comes that we set it only for _http_ protocol, but not for _https_. So if SSL is enabled it's quite easy to get HTTP 413 error. Not relevant to branch-2 nor master because it's fixed by HBASE-12894 -- This message was sent by Atlassian JIRA (v6.4.14#64029)