"This API version doesn't seem to exist"

[alexwhitman]

Below is an api definition that we're using:

{
    "name": "API",
    "api_id": "1",
    "org_id": "default",
    "definition": {
        "location": "header",
        "key": "version"
    },
    "auth": {
        "auth_header_name": "authorization"
    },
    "version_data": {
        "not_versioned": true
    },
    "proxy": {
        "listen_path": "/",
        "target_url": "http://backend:8000",
        "strip_listen_path": true
    }
}

version_data.not_versioned is set to true but hitting any route in that API returns

{
    "error": "This API version doesn't seem to exist"
}

This is running on a build of current master.

Also notice that the single quote in the string has been HTML encoded, that probably shouldn't happen. 😄

[lonelycode]

I think I may know what's wrong here, the version_data section still requires the ignored, blaklist and whitelist metadata. In a non-versioned API Tyk uses a "Default" version (the first in the list). So if you add a single version entry with empty values it should behave itself:

{
    "name": "API",
    "api_id": "1",
    "org_id": "default",
    "definition": {
        "location": "header",
        "key": "version"
    },
    "auth": {
        "auth_header_name": "authorization"
    },
    "version_data": {
        "not_versioned": true,
        "versions": {
            "default": {
                "name": "default",
                "expires": "",
                "paths": {
                    "ignored": [],
                    "white_list": [],
                    "black_list": []
                }
            }
        }
    },
    "proxy": {
        "listen_path": "/",
        "target_url": "http://backend:8000",
        "strip_listen_path": true
    }
}

Will fix the HTML encoding, that'a a little odd...

[alexwhitman]

That's done it, thanks.

[lonelycode]

Fixed HTML encoding... not ideal, but fixed, still pondering if we should switch out from HTML templates instead of text.