VERIFIED SOLUTION i
X

Resolve HTTP error when translating GML files with Universal Translator in MapInfo Pro 15 and 15.2

Issue

When translating a GML file using the Universal Translator in MapInfo Pro™ 15 and 15.2, it produces an error similar below.

Received HTTP response header: 'HTTP/1.1 404 Not Found' 
Received HTTP response header: 'Date: Thu, 04 Feb 2016 18:20:51 GMT' 
Received HTTP response header: 'Server: Apache' 
Received HTTP response header: 'Vary: Accept-Encoding' 
Received HTTP response header: 'Content-Encoding: gzip' 
Received HTTP response header: 'Content-Length: 237' 
Received HTTP response header: 'Content-Type: text/html; charset=iso-8859-1' 

User: 
Received HTTP response header: 'HTTP/1.1 404 Not Found' 

Received HTTP response header: 'Date: Wed, 27 Jan 2016 09:15:26 GMT' 

Received HTTP response header: 'Server: Apache' 

Received HTTP response header: 'Vary: Accept-Encoding' 

Received HTTP response header: 'Content-Encoding: gzip' 

Received HTTP response header: 'Content-Length: 237' 

Received HTTP response header: 'Content-Type: text/html; charset=iso-8859-1' 

Cause

This is a bug within the Universal Translator, which is provided by Safe Software.

Resolution

UPDATED: July 17, 2017


This bug has been fixed in MapInfo Pro 16. Please upgrade to this version to make use of the fix.

To try the fix out the MapInfo Pro 16 trial version can also be downloaded.

Environment Details

Products affected: MapInfo Pro

Downloads

  • No Downloads