[BUG] Mm5 and Mp1 interfaces of MEC Platform give incorrect location header

[gabrik]

MEC Platform Mm5 and Mp1 interfaces procuces a wrong URL in the location header upon a the creation of a resource

from a TCP dump

POST /exampleAPI/mm5/v1/applications/123/dns_rules HTTP/1.1
Host: 10.212.26.198:8091
Accept: */*
Connection: keep-alive
Accept-Encoding: gzip, deflate
Content-Length: 125
User-Agent: python-requests/2.9.1

{"dnsRuleId":"dnsRule2","domainName":"googledns.mec","ipAddressType":"IP_V4","ipAddress":"8.8.4.4","ttl":10,"state":"ACTIVE"}HTTP/1.1 201 Created
Server: nginx/1.14.0 (Ubuntu)
Date: Thu, 09 May 2019 10:59:38 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: keep-alive
location: /exampleAPI/mm5/v1/applications123dns_rulesdnsRule2

89
{"DnsRule":{"dnsRuleId":"dnsRule2","domainName":"googledns.mec","ipAddressType":"IP_V4","ipAddress":"8.8.4.4","ttl":10,"state":"ACTIVE"}}
0

Missing / in the URL

[gabrik]

Same Bug applies to MEAO Mm1

[gabrik]

Problem is un functions creating the urls, they are missing /
See: Mp1
Same applies for Mm5 and Mm1

Will fix in next PR with other bug Fixes to MEAO