December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4196) HTTP protocol violation

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4196: ----------------------------------- Or by adding filter to specific location like {noformat} /subsystem=undertow/server=default-server/host=default-host/location="/"/filter-ref=gzipfilter:add(predicate="path-suffix[.css, .js]") {noformat} where location is one of <location> defined under host. > HTTP protocol violation > ----------------------- > > Key: WFLY-4196 > URL: https://issues.jboss.org/browse/WFLY-4196 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 8.2.0.Final > Reporter: Nicolas Cazottes > Assignee: Stuart Douglas > Priority: Blocker > Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg > > > If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value. > Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted. > The explanation is that the web application uses a filter to compress the content in gzip format. > For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4202) Domain-level logger category add does not behave as documented

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4202?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-4202: ------------------------------------- I'm not sure if this is a bug or not, but you just need to add a leading {{/}}. {code} /profile=full-ha-osgi/subsystem=logging/logger=org.jboss.weld:add {code} > Domain-level logger category add does not behave as documented > -------------------------------------------------------------- > > Key: WFLY-4202 > URL: https://issues.jboss.org/browse/WFLY-4202 > Project: WildFly > Issue Type: Bug > Components: CLI, Logging > Affects Versions: 8.2.0.Final > Reporter: Arcadiy Ivanov > Assignee: Alexey Loubyansky > > {noformat} > [domain@localhost:9990 /] profile=full-ha-osgi/subsystem=logging/logger=org.jboss.weld:add > 'profile=full-ha-osgi/subsystem=logging/logger=org.jboss.weld:add' is not a valid operation name. > {noformat} > According to the [documentation|https://docs.jboss.org/author/display/WFLY8/How+To#HowTo-Ho...] the above should work -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4196) HTTP protocol violation

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4196: -------------------------------------- Also you can apply the subsystem level configuration to a single application by using path-prefix[/myapplication] in the predicate (so something like predicate="path-prefix[/myapplication] and path-suffix[.js]") > HTTP protocol violation > ----------------------- > > Key: WFLY-4196 > URL: https://issues.jboss.org/browse/WFLY-4196 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 8.2.0.Final > Reporter: Nicolas Cazottes > Assignee: Stuart Douglas > Priority: Blocker > Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg > > > If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value. > Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted. > The explanation is that the web application uses a filter to compress the content in gzip format. > For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4196) HTTP protocol violation

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4196: -------------------------------------- So the only spec compliant way of implementing this is to wrap the HttpServletResponse object in the filter, and then intercept and discard all calls to setContentLength and setContentLengthLong (plus the general setHeader methods for content length). Is it possible that your filter already does this, but does only does it for setContentLength and not setContentLengthLong ? This method was added in Servlet 3.1 and is used by the default servlet, so this would explain why you filter works in older versions. > HTTP protocol violation > ----------------------- > > Key: WFLY-4196 > URL: https://issues.jboss.org/browse/WFLY-4196 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 8.2.0.Final > Reporter: Nicolas Cazottes > Assignee: Stuart Douglas > Priority: Blocker > Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg > > > If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value. > Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted. > The explanation is that the web application uses a filter to compress the content in gzip format. > For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4202) Domain-level logger category add does not behave as documented

by Arcadiy Ivanov (JIRA)

Arcadiy Ivanov created WFLY-4202: ------------------------------------ Summary: Domain-level logger category add does not behave as documented Key: WFLY-4202 URL: https://issues.jboss.org/browse/WFLY-4202 Project: WildFly Issue Type: Bug Components: CLI, Logging Affects Versions: 8.2.0.Final Reporter: Arcadiy Ivanov Assignee: Alexey Loubyansky {noformat} [domain@localhost:9990 /] profile=full-ha-osgi/subsystem=logging/logger=org.jboss.weld:add 'profile=full-ha-osgi/subsystem=logging/logger=org.jboss.weld:add' is not a valid operation name. {noformat} According to the [documentation|https://docs.jboss.org/author/display/WFLY8/How+To#HowTo-Ho...] the above should work -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-25) Windows PowerShell scripts in bin

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-25?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-25: ----------------------------------- Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFCORE-25 > URL: https://issues.jboss.org/browse/WFCORE-25 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 1.0.0.Alpha16 > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-103) Add Full Kerberos Support

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-103?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-103: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Add Full Kerberos Support > ------------------------- > > Key: WFCORE-103 > URL: https://issues.jboss.org/browse/WFCORE-103 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: 1.0.0.Alpha16 > > > There are a number of steps required to full add Kerberos support - this is a top level tracking task to be resolved once all steps are complete. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-80) Upgrade org.apache.httpcomponents:httpclient to 4.3.2

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-80?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-80: ----------------------------------- Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Upgrade org.apache.httpcomponents:httpclient to 4.3.2 > ----------------------------------------------------- > > Key: WFCORE-80 > URL: https://issues.jboss.org/browse/WFCORE-80 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Affects Versions: 1.0.0.Alpha5 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 1.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-54) Add Keycloak authentication/authorization to http management endpoint

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-54?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-54: ----------------------------------- Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFCORE-54 > URL: https://issues.jboss.org/browse/WFCORE-54 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.0.0.Alpha16 > > > This is here to track the core changes needed for WFLY-3591. See that jira for details. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-31) The JBoss Modules schemas are missing from the build

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-31?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-31: ----------------------------------- Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > The JBoss Modules schemas are missing from the build > ---------------------------------------------------- > > Key: WFCORE-31 > URL: https://issues.jboss.org/browse/WFCORE-31 > Project: WildFly Core > Issue Type: Bug > Reporter: Darran Lofthouse > Assignee: Eduardo Martins > Fix For: 1.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014