Known Issues

ESVG-00018

The ESVG-00018 error code indicates a phenomenon caused by a network problem in the process of uploading a file. Therefore, it is difficult to determine the cause of the problem caused by the ESVG-00018 error code only.

Generally, when small data is sent to the server, if the HTTP error code is sent from the server to the client, the component receives the server error and can output (because it is waiting for a response). However, if a server sends an HTTP error code to a client while sending a file or data with a size greater than or equal to MB to POST, the client will not receive the server error code and will only recognize the socket connection as a boilable system error. Unlike the previous situation, since data is sent to the server before the process ends, only the socket-level error message can be checked because the response data is not received. Of course, this is not always consistent across all servers.

If you encounter the ESVG-00018 error code The first priority is to determine if there is an issue on the server side (4XX, 5XX HTTP error) when the request is made. If there is no issue at the WAS level, then you should investigate if there is something blocked by another system.

If an error occurs, re-upload a file that satisfies the following conditions, and the current problem can be identified with the difference in the result.

Files with names that are only alphanumeric and no spaces(must include the part of the file extension)
Common JPG, PNG image files with low filtering frequency on the server
Small files (<10KB)

Node.js environment not supported

DEXTUploadX5 is experiencing intermittent browser freezes and timeouts when uploading files in a Node.js + Express environment, and we have not yet found a cause for this. For this reason, we are not officially supporting Node.js until this issue is resolved.

CSS display: none issue

If the CSS property of the container object containing the component is display:none, this can cause a number of problems.

When using Chrome, Opera, or Safari, the content loaded by the object element is removed and reloaded depending on the value of the display property. This isn't a bug, but it's different from the Firefox browser, so it's ambiguous to define the correct behavior. As soon as the display property is set to none, the loaded DEXTUploadX5 component is removed, all the states of the object are lost, and the connected event also fails. Even if the display property is changed again, an empty list is shown because there are no status values already removed, and all of the previously set states are returned to their initial state.

There is currently no way to make this phenomenon work consistently regardless of display property changes. However, you must configure the screen using a method other than display.

To hide the upload area, do not use the display property, but set the width and height properties of the CSS to 0. To show the upload area again, specify the appropriate width and height values.

HEAD request issue

The DEXTUploadX5 product has a process for making HEAD requests to the server.

It is also used when the browser asks itself for the MIME type for the SVG file or asks if the file exists to download the file.

Therefore, if you restrict HEAD requests on the server, it will be difficult to use the component.

Communication failue with HD application according to 'Private Network Access' specification

'Private Network Access' refers to the contents of restricting access to the private network from external sites that do not have security applied. Since access to localhost is restricted in web applications operated by http, communication with HD applications is also affected.

Google Chrome (Microsoft Edge, Apple Safari) browsers are gradually reflecting the 'Private Network Access' specification by 2022.

When using HD application in DEXTUploadX5, using in https environment is not a problem, but in http environment, HD program installation page popup keeps popping up because communication with HD application is not possible. (In the case of a web application running on localhost, it works correctly as before.)