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 D9BFD200D1B for ; Thu, 12 Oct 2017 21:09:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D85AB160BE6; Thu, 12 Oct 2017 19:09:04 +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 2A97B160BE4 for ; Thu, 12 Oct 2017 21:09:04 +0200 (CEST) Received: (qmail 20968 invoked by uid 500); 12 Oct 2017 19:09:03 -0000 Mailing-List: contact dev-help@knox.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@knox.apache.org Delivered-To: mailing list dev@knox.apache.org Received: (qmail 20956 invoked by uid 99); 12 Oct 2017 19:09:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Oct 2017 19:09:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6D8571A1803 for ; Thu, 12 Oct 2017 19:09:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id mB35FyA1G-eW for ; Thu, 12 Oct 2017 19:09:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 65C915F2A8 for ; Thu, 12 Oct 2017 19:09: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 EECE3E0E08 for ; Thu, 12 Oct 2017 19:09: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 A91BA23F3E for ; Thu, 12 Oct 2017 19:09:00 +0000 (UTC) Date: Thu, 12 Oct 2017 19:09:00 +0000 (UTC) From: "Larry McCay (JIRA)" To: dev@knox.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KNOX-1079) Regression: proxy for Atlas fails with j_spring_security_check during login MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 12 Oct 2017 19:09:05 -0000 [ https://issues.apache.org/jira/browse/KNOX-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-1079: ------------------------------ Resolution: Fixed Status: Resolved (was: Patch Available) > Regression: proxy for Atlas fails with j_spring_security_check during login > --------------------------------------------------------------------------- > > Key: KNOX-1079 > URL: https://issues.apache.org/jira/browse/KNOX-1079 > Project: Apache Knox > Issue Type: Bug > Components: Server > Affects Versions: 0.13.0 > Reporter: Madhan Neethiraj > Assignee: Madhan Neethiraj > Priority: Critical > Fix For: 0.14.0 > > Attachments: KNOX-1079.patch > > > Reported by [~ssainath] in ATLAS-2203: > # Enabled knox proxy for Atlas. > # On accessing https://knox_gateway:8443/gateway/ui/atlas/login.jsp , 404 is thrown with the following : > POST > 404 Not Found > https://knox_gateway:8443/gateway/j_spring_security_check > and > GET > 404 Not Found > https://knox_gateway:8443/favicon.ico > which should ideally go to > https://knox_gateway:8443/gateway/ui/atlas/j_spring_security_check > [~nixonrodrigues] investigated this issue and found that a recent commit in Atlas, which changed Jetty version (ATLAS-2186), caused this regression. Here are the details from his investigation: > This regression is caused because the content type of javascript file is changed from *application/javascript* to *application/x-javascript* due to recent jetty version change in ATLAS-2186. > {noformat} > HTTP/1.1 200 OK > Date: Thu, 12 Oct 2017 13:05:08 GMT > Content-Type: application/x-javascript > Last-Modified: Wed, 11 Oct 2017 15:29:36 GMT > Accept-Ranges: bytes > Server: Jetty(8.1.19.v20160209) > Content-Encoding: gzip > Vary: Accept-Encoding, User-Agent > Content-Length: 1018 > {noformat} > [~lmccay] suggested the fix, to update rewrite.xml to recognize content-type */x-javascript as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)