afs commented on PR #2373: URL: https://github.com/apache/jena/pull/2373#issuecomment-2269387320
Hi @kinow, Reading back ... If the client is doing checking and it will give better error messages. e.g. no actual spaces !!! The server is going to check anyway but all it can say to a request is "no" or "yes". If the client side parses the URI with [uri-js](https://www.npmjs.com/package/uri-js/) that should be good. It is RFC 3986 compliant. Addition checks for common mistakes (spaces!) are nice - better error messages. Aside :: On the server side, Java java.net.URI is not good - it's more like the old [RFC 2396](https://datatracker.ietf.org/doc/html/rfc2396), not [RFC3986](https://datatracker.ietf.org/doc/html/rfc3986). Jena does not use it. Percent should be allowed end-to-end - a URI really does have `%-2-3` in it. The URI parser should be happy then when sent the request should be making it a safe - avoid applying the algorithm twice, once in Jane JS code and once by the HTTP client. The receiving code should decode the request properly once. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: pr-unsubscr...@jena.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: pr-unsubscr...@jena.apache.org For additional commands, e-mail: pr-h...@jena.apache.org
