Zanata client 3.8.3 can't push file to server running on WildFly

Description

Error when pushing/pulling files using Zanata client 3.8.3

2016-04-04 14:29:01,926 pool-4-thread-1 INFO [org.zanata.workflow.ClientWorkFlow] - [ERROR] Received invalid content type from the server. Most likely you're hitting an error page or being redirected. Please check the server URL is correct (in zanata.ini and in zanata.xml) and make sure you use the correct address.
2016-04-04 14:29:01,926 pool-4-thread-1 INFO [org.zanata.workflow.ClientWorkFlow] - [ERROR] Wrong content type received: [application/vnd.zanata.version+xml; charset=ISO-8859-1]. Content page title: []
2016-04-04 14:29:01,926 pool-4-thread-1 INFO [org.zanata.workflow.ClientWorkFlow] - [INFO]

Environment

None

Activity

Show:
Sean Flanigan
April 4, 2016, 5:42 AM
Edited

Apparently only happens when Zanata server runs under WildFly. Tested against WF 9.0.1 - we should find out if 10 is affected.

EDIT: 10 is apparently not affected. Since we package RESTEasy with the app, the difference must be in the web engine:

  • EAP 6 (JBoss Web): works with zanata-maven-plugin 3.8.3

  • WF 9 (Undertow 1.2): breaks zanata-maven-plugin 3.8.3

  • WF 10 (Undertow 1.3): works with zanata-maven-plugin 3.8.3

Sean Flanigan
April 6, 2016, 6:44 AM

For some reason WildFly 8 and 9 have been adding ";charset=ISO-8859-1" to REST responses all along. The extra content type validation added as part of was not handling the presence of charset, so I have updated the validation regex.

Ready for Release

Assignee

Unassigned

Reporter

Alex Eng

Labels

None

Tested Version/s

None

Components

Fix versions

Affects versions

Priority

High
Configure