403 Error When Downloading MIMIC-III via wget from Server Environment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 82
- Forks
- 21
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Dear PhysioNet Support Team,
I am writing to ask for your assistance regarding an issue I am encountering when downloading the MIMIC-III (v1.4) dataset.
I have completed the required CITI training and have been granted access to the MIMIC-III database. When I download the dataset directly through the PhysioNet website using a web browser, the compressed files download successfully without any issues.
However, when I attempt to download the same files using the wget command from a Linux server environment (for example, using the direct download links provided on the dataset page), the request consistently returns a 403 Forbidden error.
I would like to clarify a few points:
The download works normally via a browser on my local machine.
The issue only occurs when using wget from a remote server.
I am logged in to my PhysioNet account in the browser, but I understand that wget may not automatically carry authentication credentials or cookies.
I would like to ask:
Are there any restrictions on downloading the dataset from server or cloud-based environments? I would also like to mention that I am not in a position to use cloud services conveniently, so it would be preferable if I could download the data using wget or similar command-line tools.
I have tried several common approaches but have not yet been able to resolve the issue. Any guidance or documentation you could provide would be greatly appreciated.
Thank you very much for your time and support.
Contributor guide
No contributing guide indexed for this repository
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
The issue does not identify a repository file, test, or entry point to inspect. Start by locating the command-line download and authentication documentation or implementation, then reproduce the 403 response from a Linux server and document a supported authenticated download path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100