github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

The timezone in the last-modified header is specified incorrectly. #13433

New Issue
Closed
opened 2025-11-02 10:42:11 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 10:42:11 -06:00
Owner
Copy Link

Originally created by @phi-friday on GitHub (Aug 28, 2024).

Description

The date uses utc, but the calculated time was entered correctly.
However, last-modified is the correct time, but the timezone is specified as utc.
The same goes for the if-modified-since header in request.
The current time is 2024-08-28T04:24:31.699596+00:00,
so the last modified time of Wed, 28 Aug 2024 13:08:50 GMT is obviously wrong.

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

url: https://<some domain>/<owner>/<repo>/src/branch/main/<sub paths...>/<some file>

스크린샷 2024-08-28 오후 1 14 12

url: https://<some domain>/<owner>/<repo>/raw/branch/main/<sub paths...>/<some file>

스크린샷 2024-08-28 오후 1 14 30

Git Version

No response

Operating System

No response

How are you running Gitea?

services:
  repository:
    container_name: git-server
    image: gitea/gitea:1.22.1
    restart: always
    env_file:
      - .env
    ports:
      - "127.0.0.1:${GITEA_SSH_PORT}:22"
    networks:
      - public-network
    command:
      - sh
      - -c
      - |
        sh /init.sh
        /bin/s6-svscan /etc/s6
    environment:
      - TZ=Asia/Seoul
    volumes:
      - git-server:/data
      - type: bind
        source: "/home/${GITEA_SSH_USER_NAME}/.ssh"
        target: "/data/git/.ssh"
        read_only: false
      - type: bind
        source: "./app.ini.default"
        target: "${GITEA_APP_DEFAULT_PATH}"
        read_only: true
      - type: bind
        source: "./init.sh"
        target: "/init.sh"
        read_only: true
      - "/etc/timezone:/etc/timezone:ro"
      - "/etc/localtime:/etc/localtime:ro"
    extra_hosts:
      - ${COMMON_PROXY_LOCAL_HOST}:host-gateway
      - ${COMMON_ADDITIONAL_PROXY_LOCAL_HOST}:host-gateway
    logging:
      options:
        max-size: 10m
        max-file: 1

Database

PostgreSQL

Originally created by @phi-friday on GitHub (Aug 28, 2024). ### Description The `date` uses `utc`, but the calculated time was entered correctly. However, `last-modified` is the correct time, but the timezone is specified as `utc`. The same goes for the `if-modified-since` header in `request`. The current time is `2024-08-28T04:24:31.699596+00:00`, so the last modified time of `Wed, 28 Aug 2024 13:08:50 GMT` is obviously wrong. ### Gitea Version 1.22.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ## url: `https://<some domain>/<owner>/<repo>/src/branch/main/<sub paths...>/<some file>` ![스크린샷 2024-08-28 오후 1 14 12](https://github.com/user-attachments/assets/10aa0998-0855-4f93-ae30-bb647fd84161) ## url: `https://<some domain>/<owner>/<repo>/raw/branch/main/<sub paths...>/<some file>` ![스크린샷 2024-08-28 오후 1 14 30](https://github.com/user-attachments/assets/5850dc82-519e-4d0f-933d-b5dcea63c571) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? ```yaml services: repository: container_name: git-server image: gitea/gitea:1.22.1 restart: always env_file: - .env ports: - "127.0.0.1:${GITEA_SSH_PORT}:22" networks: - public-network command: - sh - -c - | sh /init.sh /bin/s6-svscan /etc/s6 environment: - TZ=Asia/Seoul volumes: - git-server:/data - type: bind source: "/home/${GITEA_SSH_USER_NAME}/.ssh" target: "/data/git/.ssh" read_only: false - type: bind source: "./app.ini.default" target: "${GITEA_APP_DEFAULT_PATH}" read_only: true - type: bind source: "./init.sh" target: "/init.sh" read_only: true - "/etc/timezone:/etc/timezone:ro" - "/etc/localtime:/etc/localtime:ro" extra_hosts: - ${COMMON_PROXY_LOCAL_HOST}:host-gateway - ${COMMON_ADDITIONAL_PROXY_LOCAL_HOST}:host-gateway logging: options: max-size: 10m max-file: 1 ``` ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 10:42:11 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13433
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?