sameersbn / sameersbn/docker-gitlab
Question: Enable PUT For Remote API?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I have a gitlab container running locally. This server is only intended to be accessed from the machine running it so security is not a concern. I have not enable HTTPS.
I can create projects and use GET methods via the remote API (e.g., get a list of projects) but doing e.g.:
curl -v -X PUT --header "PRIVATE-TOKEN: gj2su57CuDNTyUtBqxn2" "http://192.168.99.100/api/v3/users?username=user1&email=ekimber@example.com&password=ekimber&name=ekimber&can_create_groups=true&confirm=false"
Results in HTTP/1.1 405 Method Not Allowed
I've looked all the docs that seem relevant and googled a good bit but I can't find anything that suggests this shouldn't work.
I assume I've missed a configuration setting somewhere but I have no idea what that might be.
If there's a better place to ask this sort of question, please direct me there. I couldn't find anything.
Thanks,
Eliot
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
Start with the remote API request shown for /api/v3/users and verify whether that endpoint supports PUT in the GitLab container. Check the relevant API documentation and container configuration, then document whether the 405 response is expected or identify the setting or change needed to make the request succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100