Hi all,
why ORDS is returning status code 500 when calling an REST Data Service with Basic Authentication and incorrectly encoded user:pw string?
I had a longer session with one of my clients till I found that he isn't encoding user:pw correctly, it was hard to find, because it seems the problem is on server side.
I think you should return 400 or 401, it's not an unexpeced server error, it's an wrong use of the authorization header, so you can handle it. It's the client fault, not my as ORDS developer, I can't handle it and I can't log it in this case...
What do you think? Why are you checking the Authentication Header Parameter? I have to deal with all the user and pw things etc. in case of Basic Authentication, so it would be easier if ORDS would let it untouched, so I can handle it.
Thanks!
Lukas