Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XAdES Conformance Checker not working #37

Open
quamis opened this issue Oct 14, 2022 · 5 comments
Open

XAdES Conformance Checker not working #37

quamis opened this issue Oct 14, 2022 · 5 comments

Comments

@quamis
Copy link

quamis commented Oct 14, 2022

After I upload a file, the link that should open the report returns 404.
It was working yesterday.

@lovele0107
Copy link
Owner

lovele0107 commented Oct 14, 2022

I have just tried and had no issue. Could you please try again or at least could you share the signature that created error ?

@quamis
Copy link
Author

quamis commented Oct 14, 2022

I get this for any kind of file. In this example I've uploaded an unrelated csv file. I get the same behaviour for xml files also.

etsi.2022-10-14-2022-10-14_14.57.40.mp4

@quamis
Copy link
Author

quamis commented Oct 17, 2022

Hello,
I found the issue.
If I login with my username + a space character, the login is succesfull, but the upload paths contain the username's space in it. That means that the report path will look like this:

https://signatures-conformance-checker.etsi.org/protected/XAdESConf/TestCases/username _041234567890/123456789/index.html (notice the space after username. That path does not exist on server, so the 404 appears.

@lovele0107
Copy link
Owner

Sorry for this. Please provide me your username and I will recreate it without space

@quamis
Copy link
Author

quamis commented Oct 17, 2022

It's ok, I changed the username in the password manager, not sure how it got there with the space in the first place. But it's an easy error to make that will apparently break the upload process. Seems to me that the upload process and the generated links in the page simply needs to happen without the space chars at the end of the username, so it would probably be 1-2 lines of code to fix.

I can close this issue from my POV.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants