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

API: RFC 3339 time format as specified by Swagger not accepted #6302

New Issue
Closed
opened 2025-11-02 06:51:36 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:51:36 -06:00
Owner
Copy Link

Originally created by @DuckDuckWhale on GitHub (Nov 12, 2020).

  • Gitea version (or commit ref): 1.12.5
  • Git version: N/A
  • Operating system: Ubuntu Server 20.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Haven't tried
  • Log gist: N/A

Description

When making a request using the API to /user/times and parameter since using RFC 3339 with space instead of T, the API returns an empty message, but when using T it works fine. Lower case t also as permitted by the RFC doesn't work either.

Originally created by @DuckDuckWhale on GitHub (Nov 12, 2020). - Gitea version (or commit ref): 1.12.5 - Git version: N/A - Operating system: Ubuntu Server 20.04 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Haven't tried - Log gist: N/A ## Description When making a request using the API to `/user/times` and parameter `since` using RFC 3339 with space instead of `T`, the API returns an empty message, but when using `T` it works fine. Lower case `t` also as permitted by the RFC doesn't work either.
GiteaMirror added the reviewed/wontfix label 2025-11-02 06:51:36 -06:00
GiteaMirror commented 2025-11-02 06:51:37 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 14, 2020):

RFC 3339 specifies that T should be used. It states that space or lowercase MAY be accepted but that in now way means it should be accepted to be compatible with spec.

@lafriks commented on GitHub (Nov 14, 2020): RFC 3339 specifies that `T` should be used. It states that space or lowercase MAY be accepted but that in now way means it should be accepted to be compatible with spec.
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 reviewed/wontfix
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#6302
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?