Closed cessda-bitbucket-importer closed 1 year ago
Original comment by Taina Jääskeläinen.
Currently shows the user empty page, should give a response.
Original comment by Martin Šeleng (GitHub: pakoselo).
@Joshocan Actually it returns the 500 error, but it doesn’t show the error in the browser. The 200 is only for the page showed. I am not able to see the image, but probably is the same as mine.
Original comment by Martin Šeleng (GitHub: pakoselo).
@Joshocan Finally I was able to open it and is the same.
Original comment by Joshua Tetteh Ocansey (GitHub: Joshocan).
@pakoselo Thanks for working on this. It should not respond with 500 code for unknown CV.
it should rather return 404 code with a caption “ CV with object ${CV_name}
not found” both at the machine interface and User interface.
Do you want me to split issues into two; one for machine response and other for UI response? If you like
Original comment by Martin Šeleng (GitHub: pakoselo).
@Joshocan the problem is how the whole application is developed and it needs to redesign lot of stuff, so leave it as it is right now.
Original comment by Martin Šeleng (GitHub: pakoselo).
@Joshocan I found the solution, it is little bit weird, but efficient. Marked as resolved.
Original comment by Joshua Tetteh Ocansey (GitHub: Joshocan).
Thanks @pakoselo Has it changes being committed yet so I can test it?
Original comment by Martin Šeleng (GitHub: pakoselo).
Not yet, as the build was not running. And yet it produces test errors. Need to update tests.
Original comment by Martin Šeleng (GitHub: pakoselo).
@Joshocan It should be on staging already as the builds of the master branch were successful + you can also test issue 414. I need to redesign them little bit to be more spring oriented, but it’s ok right now.
Original comment by Joshua Tetteh Ocansey (GitHub: Joshocan).
Thanks @pakoselo
Yes, I tested it .
2. But the issue persists in the machine readable level, it still returns 200 code (see below)
Original comment by Martin Šeleng (GitHub: pakoselo).
Probably it will take more time as I didn't saw the way, how to generate an error, in every error the system generates ok I don’t see it as a problem right now.
Original comment by Joshua Tetteh Ocansey (GitHub: Joshocan).
@pakoselo In that case, I will separate the issues and close this issue for UI
Original comment by Martin Šeleng (GitHub: pakoselo).
@Joshocan you got the curl message wrong. The reason why the result is 200 is, that it returns the webpage with the error message and the status must be 200. Because the webpage is displayed correctly. You will get the error only, when you don't implement the 404 page at your site (e.g. https://chess.sk/dsafadsf). But we are displaying the menu and everything correctly, only informing the user about the error.
Original report on BitBucket by Joshua Tetteh Ocansey (GitHub: Joshocan).
It should rather respond with 404 with a message as :
It has an impact on what the user sees in UI as well when it tries to search for the wrong CV