Skip to content

Conversation

@gocanto
Copy link
Collaborator

@gocanto gocanto commented Jul 25, 2025

Summary by CodeRabbit

  • New Features
    • Expanded CORS support to allow the "If-None-Match" HTTP header in cross-origin requests and preflight checks for both local and production environments. This enables smoother integration with clients that use this header.
    • Added exposure of the "ETag" header in cross-origin responses to improve client-side caching and validation.

@coderabbitai
Copy link

coderabbitai bot commented Jul 25, 2025

Walkthrough

The Caddy server configuration files for both local and production environments were updated to include the "If-None-Match" HTTP header in the Access-Control-Allow-Headers directive for CORS. This change was applied in both the general and preflight OPTIONS request header blocks. Additionally, the "ETag" header was exposed via Access-Control-Expose-Headers in the general header blocks. No other logic or configuration was altered.

Changes

File(s) Change Summary
caddy/Caddyfile.local Added "If-None-Match" to Access-Control-Allow-Headers and added Access-Control-Expose-Headers "ETag" in general and OPTIONS blocks
caddy/Caddyfile.prod Added "If-None-Match" to Access-Control-Allow-Headers and added Access-Control-Expose-Headers "ETag" in general and OPTIONS blocks

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • [hotfix] Caddy CORS #62: Extends the CORS configuration by adding "If-None-Match" to the allowed headers in the same Caddyfile locations, directly continuing and enhancing the same configuration.

Poem

A header hops into the list,
"If-None-Match" now can't be missed.
CORS gates swing open wide,
Letting new requests inside.
With configs neat and tidy,
The server's feeling sprightly—
Hooray for headers, signed: the rabbit, lightly! 🐇

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5bcc25 and c4e0091.

📒 Files selected for processing (2)
  • caddy/Caddyfile.local (2 hunks)
  • caddy/Caddyfile.prod (2 hunks)
✅ Files skipped from review due to trivial changes (2)
  • caddy/Caddyfile.prod
  • caddy/Caddyfile.local
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch hotfix/If-None-Match

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @gocanto, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the Caddy server configurations for both local development and production environments. The primary goal is to extend Cross-Origin Resource Sharing (CORS) support by explicitly allowing the If-None-Match HTTP header, which is crucial for enabling efficient client-side caching mechanisms like ETags.

Highlights

  • CORS Header Expansion: I've updated the Access-Control-Allow-Headers directive in both caddy/Caddyfile.local and caddy/Caddyfile.prod to include If-None-Match. This change ensures that clients can send If-None-Match headers in their cross-origin requests, facilitating proper ETag-based caching.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds the If-None-Match header to the Access-Control-Allow-Headers in the Caddy configuration for both local and production environments. The review suggests refactoring the Caddy configuration to avoid duplicating the list of allowed headers, which would improve maintainability.

@gocanto gocanto changed the title wip [hotfix] CORS/cache headers Jul 25, 2025
@gocanto gocanto merged commit 1437dba into main Jul 25, 2025
4 checks passed
@gocanto gocanto deleted the hotfix/If-None-Match branch July 25, 2025 03:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants