nginx rewrite rule example in Install > Containers is broken
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 106
- Forks
- 190
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
The nginx rewrite rule is broken. Deploying with this configuration you will not be able to login due to backend error:
/++api++/POST_application_json_
backend_1 | Traceback (innermost last):
backend_1 | Module ZPublisher.WSGIPublisher, line 167, in transaction_pubevents
backend_1 | Module ZPublisher.WSGIPublisher, line 376, in publish_module
backend_1 | Module ZPublisher.WSGIPublisher, line 271, in publish
backend_1 | Module ZPublisher.mapply, line 85, in mapply
backend_1 | Module ZPublisher.WSGIPublisher, line 68, in call_object
backend_1 | Module plone.rest.service, line 22, in __call__
backend_1 | Module plone.restapi.services, line 19, in render
backend_1 | Module plone.restapi.services.content.add, line 41, in reply
backend_1 | zExceptions.BadRequest: Property '@type' is required
Instead, this works as expected: https://6.dev-docs.plone.org/volto/deploying/seamless-mode.html#nginx-example-config-for-seamless-mode-deployments
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
Open the Install > Containers documentation and locate the nginx rewrite rule example. Compare it with the working configuration in the linked seamless-mode deployment example, then verify that the corrected configuration allows login without the reported backend error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100