[Bug] [Resource] Failed to upload file

[JohnZp]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

The bug is that when re uploading files, it will prompt file extension cannot not change

What you expected to happen

work well

How to reproduce

Anything else

No response

Version

dev

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[SbloodyS]

Please provide reproduce steps and deployment environment. I can not reproduce this issue locally.

[JohnZp]

Please provide reproduce steps and deployment environment. I can not reproduce this issue locally.

The second bug is a security interception issue, not a problem with the dolphinscheduler. I have already removed it.
The first bug occurred when the wrong method was used to retrieve the file name when re uploading the problem code. Maybe it should like this

        if (!Objects.equals(
                Files.getFileExtension(
                        file.getOriginalFilename() == null ? file.getName() : file.getOriginalFilename()),
                Files.getFileExtension(updateFileDto.getFileAbsolutePath()))) {
            throw new ServiceException("file extension cannot not change");
        }

[SbloodyS]

Did you mean reupload function error? @JohnZp

[JohnZp]

Did you mean reupload function error? @JohnZp

yes

[SbloodyS]

The second bug is a security interception issue, not a problem with the dolphinscheduler. I have already removed it. The first bug occurred when the wrong method was used to retrieve the file name when re uploading the problem code. Maybe it should like this

        if (!Objects.equals(
                Files.getFileExtension(
                        file.getOriginalFilename() == null ? file.getName() : file.getOriginalFilename()),
                Files.getFileExtension(updateFileDto.getFileAbsolutePath()))) {
            throw new ServiceException("file extension cannot not change");
        }

I've reproduce this error successfully. You got it. Would you like to fix it? @JohnZp