DataPower

 View Only

 Request with HEAD method is being triggered automatically from Datapower Cache Service

R K's profile image
R K posted Mon September 22, 2025 08:58 AM
Dears,

I have an integration in Datapower where cache mechanism was implemented to store the data received from DB.

Service A(WSP) -> ServiceB(Cache through DocumentCache)  -> If cache not available -> Service C(MPGW) -> DB

The below logs are being recorded in Datapower for the Service C. It suggests that there is HEAD Method call happening to this service from Service B but there is no implementation in application side. How can this be avoided and what is the reason for this HEAD method transaction?


[0x01130024][mpgw][error] mpgw(Service C): trans(981614751)[error]: Request did not match allowed-feature list
[0x80e00139][mpgw][error] source-http(httphandler): trans(981614751): Request requires HEAD in allowed-features list, which is not currently configured.
[0x01130024][mpgw][error] mpgw(Service C): trans(981614751)[error]: Request did not match allowed-feature list
Ajitabh Sharma's profile image
Ajitabh Sharma posted Tue September 23, 2025 01:02 AM

HEAD is for getting metadata, a kind of sneak peek into the content without actually reading the content. See HEAD request method - HTTP | MDN. It is not uncommon in caching scenario for it to creep up. Best way to keep it enabled in FSH. 

R K's profile image
R K posted Tue September 23, 2025 09:06 AM

Dear Ajitabh, Thanks for the reply. However, is there any way to suppress this transaction from Datapower Cache service

Joseph Morgan's profile image
Joseph Morgan posted Tue September 23, 2025 09:55 AM

Without knowing how Service B calls Service C, it is difficult to know if there is a way to avoid the HEAD request.  DataPower can sometimes be frustratingly proper and may not can be avoided.

Unless it is causing problems to allow it, take @Ajitabh Sharma's advice and just keep it.  

Related Content