OpenRefine / OpenRefine/OpenRefine
Support HTTP Basic Authentication in project creation by URL download
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12k
- Forks
- 2.2k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 27
Description
Original author: mcnamara.tim@gmail.com (November 15, 2010 22:09:42)
What steps will reproduce the problem?
- Start project with https://demogy.service-now.com/incident.do?CSV
- Receive 401 warning
What is the expected output? What do you see instead?
There are a few possible fixes. First, we could provide an error message with more detail for non-technical users. E.g. on a 401 error say that credentials are needed, rather than simply failing. Secondly, the product could provide somewhere to add in credentials.
Original issue: http://code.google.com/p/google-refine/issues/detail?id=217
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce project creation with the HTTPS URL in the issue and inspect the project-creation download path that handles the 401 response. Determine whether the completed change should provide a clearer credentials-needed error, a place to enter credentials, or both, and verify the chosen behavior against the reported URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100