-
Notifications
You must be signed in to change notification settings - Fork 56
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
How to show actual URL called #157
Comments
using dev tools is not an option for you? I guess you are using node.js sever to server? Maybe you can simply add a log to the node_modules/o.js source code:
|
I found out that the error is because of spaces being replaced with plus symbols: becomes: which looks like a perfectly fine URL, but OData allows query like syntax so + is a reserved character.
OData Version 4.0 Part 2: URL Conventions
|
Just finished testing. Everything works great with I successfully processed 900K objects from a Denodo OData API, and the code is clean thanks to Since version |
yeah, as said... time management... but I just released version 2.0.0 5h ago 🥳 |
How can I log the actual URL the
o.js
client is calling?I have a non trivial GET request (multiple $expand, $select, $filter, $orderby etc.) which returns an error from the odata API.
When I constructed the URL with Postman, it worked fine, but in code, what should be the same thing, returns the following error which doesn't make any sense:
I tested constructing the URL myself and passing it to the
o.js
client, and it works as expected.The text was updated successfully, but these errors were encountered: