Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
URL not working - 400 Bad Request Error
See original GitHub issueI’m trying to open SharePoint videos using its REST APIs. Below is a valid URL to a video content on SharePoint but it is giving us 400 bad request error
https://TENANT-URL/sites/retail/RETAIL/_api/web/GetFileByServerRelativeUrl('/sites/retail/retail/Video Trainings/A Caregiver''s Journey/A Caregiver''s Journey.mp4')/$value
I have using encoding the URL but it is not working either.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Fix a 400 Bad Request Error: 8 Easy Methods
One of the most common causes of HTTP status 400 bad request error is a wrong URL. This may include a mistyped URL,...
Read more >How to Fix the 400 Bad Request Error - Lifewire
Check for errors in the URL. The most common reason for a 400 Bad Request error is because the URL was typed wrong...
Read more >How to Fix a 400 Bad Request Error (Causes and Fixes) - Kinsta
The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived...
Read more >400 Bad Request Error: What It Is and How to Fix It
As mentioned, the most common cause of a 400 Bad Request is simply inputting an incorrect URL. Domain names (e.g. airbrake.io) are case- ......
Read more >What is a 400 Bad Request Error (and How Can I Fix It)?
A 400 Bad Request Error occurs when a request sent to the website server is incorrect or corrupt, and the server receiving the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
OkHttpClient worked like a charm.
Thanks mate!
I can’t say for sure, but my assumption is that Samsung has modified the http client on that device that has caused a bug.