Public bug reported: GET /v2.0/networks/{network_id} API responds with \u escaped Unicode characters even though the request headers specify that the client will only accept UTF-8 encdoding.
Both these headers were tried, with same result : “Accept: application/json;charset=UTF-8” and “Accept-Charset: UTF-8” We observer a similar behavior for subnets API as well. GET Request: http://172.24.35.1:9696/v2.0/networks RESPONSE of GET Request: http://172.24.35.1:9696/v2.0/networks {"networks": [{"status": "ACTIVE", "router:external": true, "availability_zone_hints": [], "availability_zones": ["nova"], "description": "", "provider:physical_network": "extnet", "subnets": ["1afd5d0c-b5bd-4267-af39-2d81d44437c4"], "name": "\u7f51\u7edc1external_network", "created_at": "2017-01-25T16:44:08", "tags": [], "updated_at": "2017-02-24T00:32:41", "provider:network_type": "flat", "ipv6_address_scope": null, "tenant_id": "345a6e236e414020b39807a657f41d0f", "admin_state_up": true, "ipv4_address_scope": null, "is_default": false, "shared": true, "mtu": 1500, "id": "bf1c7000-73d4-4daa-90cf-0fb24360ee61", "provider:segmentation_id": null}, {"status": "ACTIVE", "subnets": ["38166705-27fb-49d2-abc6-4d1d079f6086"], "availability_zone_hints": [], "availability_zones": ["nova"], "name": "\u7f51\u7edc2private_network", "provider:physical_network": null, "admin_state_up": true, "tenant_id": "345a6e236e414020b39807a657f41d0f", "created_at": "2017-01-25T16:45:40", "tags": [], "updated_at": "2017-02-24T00:32:55", "ipv6_address_scope": null, "description": "", "router:external": false, "provider:network_type": "vxlan", "ipv4_address_scope": null, "shared": true, "mtu": 1450, "id": "afb9f44a-4eb2-4544-8326-3334c540667f", "provider:segmentation_id": 22}, {"status": "ACTIVE", "subnets": ["80888752-c11a-4eb2-b52c-b3c036546073"], "availability_zone_hints": [], "availability_zones": ["nova"], "name": "backend_network", "provider:physical_network": null, "admin_state_up": true, "tenant_id": "345a6e236e414020b39807a657f41d0f", "created_at": "2017-01-25T19:00:30", "tags": [], "updated_at": "2017-01-26T01:37:39", "ipv6_address_scope": null, "description": "", "router:external": false, "provider:network_type": "vxlan", "ipv4_address_scope": null, "shared": true, "mtu": 1450, "id": "234b6ee3-5f6e-4841-a409-8240352d2a64", "provider:segmentation_id": 13}]} ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1672485 Title: Neutron APIs respond with Unicode characters ignoring charset in request headers Status in neutron: New Bug description: GET /v2.0/networks/{network_id} API responds with \u escaped Unicode characters even though the request headers specify that the client will only accept UTF-8 encdoding. Both these headers were tried, with same result : “Accept: application/json;charset=UTF-8” and “Accept-Charset: UTF-8” We observer a similar behavior for subnets API as well. GET Request: http://172.24.35.1:9696/v2.0/networks RESPONSE of GET Request: http://172.24.35.1:9696/v2.0/networks {"networks": [{"status": "ACTIVE", "router:external": true, "availability_zone_hints": [], "availability_zones": ["nova"], "description": "", "provider:physical_network": "extnet", "subnets": ["1afd5d0c-b5bd-4267-af39-2d81d44437c4"], "name": "\u7f51\u7edc1external_network", "created_at": "2017-01-25T16:44:08", "tags": [], "updated_at": "2017-02-24T00:32:41", "provider:network_type": "flat", "ipv6_address_scope": null, "tenant_id": "345a6e236e414020b39807a657f41d0f", "admin_state_up": true, "ipv4_address_scope": null, "is_default": false, "shared": true, "mtu": 1500, "id": "bf1c7000-73d4-4daa-90cf-0fb24360ee61", "provider:segmentation_id": null}, {"status": "ACTIVE", "subnets": ["38166705-27fb-49d2-abc6-4d1d079f6086"], "availability_zone_hints": [], "availability_zones": ["nova"], "name": "\u7f51\u7edc2private_network", "provider:physical_network": null, "admin_state_up": true, "tenant_id": "345a6e236e414020b39807a657f41d0f", "created_at": "2017-01-25T16:45:40", "tags": [], "updated_at": "2017-02-24T00:32:55", "ipv6_address_scope": null, "description": "", "router:external": false, "provider:network_type": "vxlan", "ipv4_address_scope": null, "shared": true, "mtu": 1450, "id": "afb9f44a-4eb2-4544-8326-3334c540667f", "provider:segmentation_id": 22}, {"status": "ACTIVE", "subnets": ["80888752-c11a-4eb2-b52c-b3c036546073"], "availability_zone_hints": [], "availability_zones": ["nova"], "name": "backend_network", "provider:physical_network": null, "admin_state_up": true, "tenant_id": "345a6e236e414020b39807a657f41d0f", "created_at": "2017-01-25T19:00:30", "tags": [], "updated_at": "2017-01-26T01:37:39", "ipv6_address_scope": null, "description": "", "router:external": false, "provider:network_type": "vxlan", "ipv4_address_scope": null, "shared": true, "mtu": 1450, "id": "234b6ee3-5f6e-4841-a409-8240352d2a64", "provider:segmentation_id": 13}]} To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1672485/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp