Empty String for Flavor Id Causes 500 status

Bug #1406609 reported by William Brothers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Poppy
Fix Released
Medium
Amit Gandhi

Bug Description

Post request with an empty string ("") for the flavor_id property :
{
    "name": "Bill",
    "domains": [
        {
            "domain": "www.mywebsite.com"
        },
        {
            "domain": "blog.mywebsite.com"
        }
    ],
    "origins": [
        {
            "origin": "mywebsite.com",
            "port": 80,
            "ssl": false
        }
    ],
    "caching": [
        {
            "name": "default",
            "ttl": 3600
        },
        {
            "name": "home",
            "ttl": 17200,
            "rules": [
                {
                    "name": "index",
                    "request_url": "/index.htm"
                }
            ]
        },
        {
            "name": "images",
            "ttl": 12800,
            "rules": [
                {
                    "name": "images",
                    "request_url": "*.png"
                }
            ]
        }
    ],
    "restrictions": [
        {
            "name": "website only",
            "rules": [
                {
                    "name": "mywebsite.com",
                    "referrer": "www.mywebsite.com"
                }
            ]
        }
    ],
    "flavor_id": ""
}

And the system returned a 500 status with the following message:

{
"message": "The server encountered an unexpected condition which prevented it from fulfilling the request."
}

Revision history for this message
Amit Gandhi (amit-gandhi) wrote :
Changed in poppy:
status: New → In Progress
assignee: nobody → Amit Gandhi (amit-gandhi)
milestone: none → kilo-2
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to poppy (master)

Reviewed: https://review.openstack.org/145072
Committed: https://git.openstack.org/cgit/stackforge/poppy/commit/?id=e017ab6fda7c3e694440fc8bb7013bdfb7eb29c3
Submitter: Jenkins
Branch: master

commit e017ab6fda7c3e694440fc8bb7013bdfb7eb29c3
Author: amitgandhinz <email address hidden>
Date: Mon Jan 5 16:51:12 2015 -0500

    Set restrictions on field lengths

    Change-Id: I71290527ef344981b7901781afddb0c4102074c8
    Closes-Bug: 1406619
    Closes-Bug: 1406609

Changed in poppy:
status: In Progress → Fix Committed
Changed in poppy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.