chef / chef/chef-server

CORS support

Open
#6 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect: Security Status: To be prioritized Type: Enhancement
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

As a user, I would like Chef server responses to contain Cross Origin Resource Sharing headers so I can use the Chef server with HTTP clients that have a same-origin security policy.

This could be implemented by including some Nginx configuration and attributes in the configuration that could customize that configuration for my Chef server.

Basic support for this is enabled in Chef Zero.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Chef Zero implementation in lib/chef_zero/server.rb and the referenced Nginx CORS configuration. Then locate Chef Server's Nginx configuration and its customizable attributes. Done means Chef Server responses include configurable Cross-Origin Resource Sharing headers for clients with same-origin restrictions.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang, nginx
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.