Multiple issues identified during TTF043 validation of MEC 015 APIs in ETSI MEC Sandbox
## Summary
Multiple issues were identified during TTF043 Task-5 validation on the ETSI MEC Sandbox. These issues relate to improper HTTP response handling, missing headers, and incorrect field values across Bandwidth Management and Multi-access Traffic Steering APIs.
---
## Issues by Test Case
### 1. Incorrect HTTP 200 Instead of 404 for Unknown Parameters (Bandwidth Management API)
**Test Cases:**
- `TC_MEC_MEC015_SRV_TM_001_NF_01` (unknown `app_instance_id`)
- `TC_MEC_MEC015_SRV_TM_001_NF_02` (unknown `app_name`)
- `TC_MEC_MEC015_SRV_TM_001_NF_03` (unknown `session_id`)
**Expected Behavior:**
`404 Not Found` when querying with unknown parameters.
**Observed Behavior:**
Sandbox returns an empty list with `200 OK`.
---
### 2. Missing `Location` Header in POST Response
**Test Cases:**
- `TC_MEC_MEC015_SRV_TM_002_OK`
- `TC_MEC_MEC015_SRV_TM_003_OK`
**Expected Behavior:**
Response should include a `Location` header with the URI of the created bandwidth allocation resource.
**Observed Behavior:**
`Location` header is missing.
---
### 3. Missing Error on Invalid `sessionFilter` (PUT)
**Test Case:**
- `TC_MEC_MEC015_SRV_TM_004_BR_01`
**Expected Behavior:**
If `sessionFilter` is present for an application-specific session, the IUT must respond with `400 Bad Request`.
**Observed Behavior:**
Request is accepted, and no error is returned.
---
### 4. `allocationDirection` Field Missing in PATCH Response
**Test Case:**
- `TC_MEC_MEC015_SRV_TM_005_OK`
**Expected Behavior:**
PATCH response should return updated `allocationDirection` (e.g., `Downlink`).
**Observed Behavior:**
`allocationDirection` is returned as an empty string.
---
### 5. Null `FlowFilter` in MTS Session Info (Application-Specific)
**Test Case:**
- `TC_MEC_MEC015_SRV_MTS_002_OK_01`
**Expected Behavior:**
A valid `FlowFilter` or an intentionally omitted field should be returned.
**Observed Behavior:**
`FlowFilter` field is returned as `null`.
---
### 6. Incorrect 200 OK for Unknown `app_instance_id` in MTS Query
**Test Case:**
- `TC_MEC_MEC015_SRV_MTS_002_NF`
**Expected Behavior:**
`404 Not Found` with `problemDetails` body.
**Observed Behavior:**
Sandbox returns `200 OK` with an empty list.
---
## Recommendation
Update the MEC Sandbox implementation to ensure:
- Proper HTTP error codes (e.g., 404, 400) are returned as per ME API spec.
- `Location` headers are included on successful POSTs.
- Response payloads return complete and accurate field values.
issue