[PR #1] [MERGED] Add cache-control headers for API methods #6

New issue

Closed

opened 2026-03-04 14:56:13 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 14:56:13 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/futurice/alley-oop/pull/1
Author: @jareware
Created: 3/16/2018
Status: ✅ Merged
Merged: 3/19/2018
Merged by: @jvah

Base: master ← Head: patch-1

📝 Commits (1)

4ab9b06 Add cache-control headers for API methods

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

📝 api.go (+5 -0)

📄 Description

Unless you disagree, it might be convenient to tell the clients to never cache any of the responses.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/futurice/alley-oop/pull/1 **Author:** [@jareware](https://github.com/jareware) **Created:** 3/16/2018 **Status:** ✅ Merged **Merged:** 3/19/2018 **Merged by:** [@jvah](https://github.com/jvah) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`4ab9b06`](https://github.com/futurice/alley-oop/commit/4ab9b06249375a10a31a7cff79d203bbba5ca663) Add cache-control headers for API methods ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `api.go` (+5 -0) </details> ### 📄 Description Unless you disagree, it might be convenient to tell the clients to never cache any of the responses. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-04 14:56:13 +03:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/alley-oop#6

No description provided.

Rows
Columns