Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

Divisions in TO API uses non-RFC3339 date/time strings #7611

@jagan-parthiban

Description

@jagan-parthiban

Parent Issue: #5911

Breaking down the parent issue #5911 in smaller issues to raise separate, reviewable PRs for each of the services.

Traffic Control components affected:

  • Traffic Ops
  • Documentation

Current behavior:

Divisions Using Deprecated TimeNoMod & TimeLayout

curl --request GET \
  --url https://localhost:8443/api/4.1/divisions


{
	"response": [
		{
			"id": 33,
			"lastUpdated": "2023-05-19 09:39:09+05",
			"name": "Chennai"
		},
		{
			"id": 34,
			"lastUpdated": "2023-06-26 15:29:31+05",
			"name": "Mumbai"
		}
	]
}

Expected behavior:

Divisions to Use RFC3339 Format

curl --request GET \
  --url https://localhost:8443/api/5.0/divisions


{
	"response": [
		{
			"id": 33,
			"lastUpdated": "2023-05-19T09:39:09.761097+05:30",
			"name": "Chennai"
		},
		{
			"id": 34,
			"lastUpdated": "2023-06-26T15:29:31.872822+05:30",
			"name": "Mumbai"
		}
	]
}

Steps to reproduce:

Make the above api call to 4.1 version

Metadata

Metadata

Assignees

No one assigned

    Labels

    Traffic Opsrelated to Traffic Opslow difficultythe estimated level of effort to resolve this issue is lowlow impactaffects only a small portion of a CDN, and cannot itself break onetech debtrework due to choosing easy/limited solution

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions