[08-Dec-2022 00:03:24 Asia/Calcutta] Notification request XML => 716537259715449714661786REN325App [08-Dec-2022 00:03:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:10:06 Asia/Calcutta] Notification request XML => 716540371670438368634c316793c19715438860651786SUB00App [08-Dec-2022 00:10:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:11:07 Asia/Calcutta] Notification request XML => 716540759715088138701786REN325App [08-Dec-2022 00:11:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:12:07 Asia/Calcutta] Notification request XML => 716541041670438496093c316796c19715674370761786SUB00App [08-Dec-2022 00:12:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:16:22 Asia/Calcutta] Notification request XML => 716542931670438741592c316804c19715050723631786SUB00App [08-Dec-2022 00:16:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:17:31 Asia/Calcutta] Notification request XML => 716542939715050723631786UNSUB00App [08-Dec-2022 00:17:31 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:22:55 Asia/Calcutta] Notification request XML => 716547139715082576551786REN325App [08-Dec-2022 00:22:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:31:07 Asia/Calcutta] Notification request XML => 716549359715628435501786REN325App [08-Dec-2022 00:31:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:37:13 Asia/Calcutta] Notification request XML => 716550881670439994697c316830c19715675618251786SUB00App [08-Dec-2022 00:37:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 00:39:32 Asia/Calcutta] Notification request XML => 716551551670440129903c316833c19715457370451786SUB00App [08-Dec-2022 00:39:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:04:24 Asia/Calcutta] Notification request XML => 716561131670441586289c316862c19715437838291786SUB00App [08-Dec-2022 01:04:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:10:59 Asia/Calcutta] Notification request XML => 716566891670442025177c316881c19715082124971786SUB00App [08-Dec-2022 01:10:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:11:17 Asia/Calcutta] Notification request XML => 716567119715654215691786REN325App [08-Dec-2022 01:11:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:21:33 Asia/Calcutta] Notification request XML => 716573519715581721081786REN325App [08-Dec-2022 01:21:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:21:33 Asia/Calcutta] Notification request XML => 716573579715670123521786REN31App [08-Dec-2022 01:21:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:21:34 Asia/Calcutta] Notification request XML => 716573599715632025341786REN325App [08-Dec-2022 01:21:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:22:02 Asia/Calcutta] Notification request XML => 716573709715097249361786REN325App [08-Dec-2022 01:22:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:22:02 Asia/Calcutta] Notification request XML => 716573729715019656451786REN96App [08-Dec-2022 01:22:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:22:02 Asia/Calcutta] Notification request XML => 716573809715611928101786REN325App [08-Dec-2022 01:22:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:12 Asia/Calcutta] Notification request XML => [08-Dec-2022 01:52:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:58 Asia/Calcutta] Notification request XML => 3733830609715688672751786UNSUBG260App [08-Dec-2022 01:52:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:58 Asia/Calcutta] Notification request XML => 3733790209715026524461786UNSUBG261App [08-Dec-2022 01:52:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:59 Asia/Calcutta] Notification request XML => 3733672009715680115051786UNSUBG325App [08-Dec-2022 01:52:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:59 Asia/Calcutta] Notification request XML => 3732108109715074071141786UNSUBG325App [08-Dec-2022 01:52:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:59 Asia/Calcutta] Notification request XML => 3731250609715079661981786UNSUBG325App [08-Dec-2022 01:52:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:59 Asia/Calcutta] Notification request XML => 3730087309715025246541786UNSUBG75App [08-Dec-2022 01:52:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:52:59 Asia/Calcutta] Notification request XML => 3730017809715682298251786UNSUBG247App [08-Dec-2022 01:52:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:53:00 Asia/Calcutta] Notification request XML => 3730009409715436447251786UNSUBG166App [08-Dec-2022 01:53:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:53:00 Asia/Calcutta] Notification request XML => 3724476109715024214381786UNSUBG175App [08-Dec-2022 01:53:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:53:00 Asia/Calcutta] Notification request XML => 3707254109715648765051786UNSUBG174App [08-Dec-2022 01:53:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:53:00 Asia/Calcutta] Notification request XML => 3707122509715459923901786UNSUBG163App [08-Dec-2022 01:53:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:53:00 Asia/Calcutta] Notification request XML => 3707012009715019368951786UNSUBG81App [08-Dec-2022 01:53:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 01:53:01 Asia/Calcutta] Notification request XML => 3706934509715096357971786UNSUBG323App [08-Dec-2022 01:53:01 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:14:59 Asia/Calcutta] Notification request XML => 716705979715653001361786REN325App [08-Dec-2022 02:14:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:06 Asia/Calcutta] Notification request XML => 716706339715099912891786REN325App [08-Dec-2022 02:15:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:08 Asia/Calcutta] Notification request XML => 716706609715088936311786REN325App [08-Dec-2022 02:15:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:08 Asia/Calcutta] Notification request XML => 716706639715633678701786REN325App [08-Dec-2022 02:15:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:12 Asia/Calcutta] Notification request XML => 716706929715430608631786REN325App [08-Dec-2022 02:15:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:20 Asia/Calcutta] Notification request XML => 716707239715080201051786REN325App [08-Dec-2022 02:15:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:37 Asia/Calcutta] Notification request XML => 716708219715612286791786REN325App [08-Dec-2022 02:15:37 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:42 Asia/Calcutta] Notification request XML => 716708529715632144961786REN114App [08-Dec-2022 02:15:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:51 Asia/Calcutta] Notification request XML => 716708939715057915171786REN325App [08-Dec-2022 02:15:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:53 Asia/Calcutta] Notification request XML => 716709129715071714631786REN325App [08-Dec-2022 02:15:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:15:56 Asia/Calcutta] Notification request XML => 716709379715077444471786REN325App [08-Dec-2022 02:15:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:03 Asia/Calcutta] Notification request XML => 716709749715078590071786REN325App [08-Dec-2022 02:16:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:03 Asia/Calcutta] Notification request XML => 716709809715476779841786REN325App [08-Dec-2022 02:16:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:08 Asia/Calcutta] Notification request XML => 716710149715091874731786REN325App [08-Dec-2022 02:16:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:08 Asia/Calcutta] Notification request XML => 716710249715041848811786REN325App [08-Dec-2022 02:16:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:16 Asia/Calcutta] Notification request XML => 716710639715630914511786REN325App [08-Dec-2022 02:16:16 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:19 Asia/Calcutta] Notification request XML => 716710819715633598981786REN325App [08-Dec-2022 02:16:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:22 Asia/Calcutta] Notification request XML => 716711129715683961031786REN325App [08-Dec-2022 02:16:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:27 Asia/Calcutta] Notification request XML => 716711449715063137481786REN325App [08-Dec-2022 02:16:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:33 Asia/Calcutta] Notification request XML => 716712109715050291871786REN325App [08-Dec-2022 02:16:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:40 Asia/Calcutta] Notification request XML => 716712429715677115481786REN325App [08-Dec-2022 02:16:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:42 Asia/Calcutta] Notification request XML => 716712609715616688031786REN325App [08-Dec-2022 02:16:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:43 Asia/Calcutta] Notification request XML => 716712709715096278401786REN325App [08-Dec-2022 02:16:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:16:51 Asia/Calcutta] Notification request XML => 716713209715017707701786REN325App [08-Dec-2022 02:16:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:00 Asia/Calcutta] Notification request XML => 716713689715079506611786REN325App [08-Dec-2022 02:17:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:06 Asia/Calcutta] Notification request XML => 716714029715612732891786REN325App [08-Dec-2022 02:17:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:11 Asia/Calcutta] Notification request XML => 716714179715062114621786REN325App [08-Dec-2022 02:17:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:12 Asia/Calcutta] Notification request XML => 716714379715420000481786REN325App [08-Dec-2022 02:17:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:17 Asia/Calcutta] Notification request XML => 716714719715082100011786REN325App [08-Dec-2022 02:17:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:24 Asia/Calcutta] Notification request XML => 716715089715073374541786REN325App [08-Dec-2022 02:17:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:30 Asia/Calcutta] Notification request XML => 716715449715435250891786REN325App [08-Dec-2022 02:17:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:34 Asia/Calcutta] Notification request XML => 716715809715618278881786REN325App [08-Dec-2022 02:17:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:40 Asia/Calcutta] Notification request XML => 716716149715499868291786REN325App [08-Dec-2022 02:17:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:47 Asia/Calcutta] Notification request XML => 716716589715547977791786REN325App [08-Dec-2022 02:17:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:52 Asia/Calcutta] Notification request XML => 716716979715636715761786REN325App [08-Dec-2022 02:17:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:55 Asia/Calcutta] Notification request XML => 716717379715058880621786REN325App [08-Dec-2022 02:17:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:17:59 Asia/Calcutta] Notification request XML => 716717679715622621001786REN325App [08-Dec-2022 02:17:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:03 Asia/Calcutta] Notification request XML => 716718069715444691321786REN325App [08-Dec-2022 02:18:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:06 Asia/Calcutta] Notification request XML => 716718359715070844861786REN325App [08-Dec-2022 02:18:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:09 Asia/Calcutta] Notification request XML => 716718719715053594031786REN325App [08-Dec-2022 02:18:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:13 Asia/Calcutta] Notification request XML => 716719059715061401641786REN325App [08-Dec-2022 02:18:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:19 Asia/Calcutta] Notification request XML => 716719419715071452571786REN264App [08-Dec-2022 02:18:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:23 Asia/Calcutta] Notification request XML => 716719639715640011101786REN325App [08-Dec-2022 02:18:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:26 Asia/Calcutta] Notification request XML => 716719939715660779841786REN325App [08-Dec-2022 02:18:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:27 Asia/Calcutta] Notification request XML => 716719989715069437731786REN325App [08-Dec-2022 02:18:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:35 Asia/Calcutta] Notification request XML => 716720319715063769991786REN325App [08-Dec-2022 02:18:35 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:36 Asia/Calcutta] Notification request XML => 716720409715077757511786REN325App [08-Dec-2022 02:18:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:44 Asia/Calcutta] Notification request XML => 716720829715042465681786REN325App [08-Dec-2022 02:18:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:47 Asia/Calcutta] Notification request XML => 716721049715022815551786REN325App [08-Dec-2022 02:18:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:53 Asia/Calcutta] Notification request XML => 716721439715011278871786REN325App [08-Dec-2022 02:18:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:18:58 Asia/Calcutta] Notification request XML => 716721879715571362571786REN325App [08-Dec-2022 02:18:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:02 Asia/Calcutta] Notification request XML => 716722239715068931851786REN325App [08-Dec-2022 02:19:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:06 Asia/Calcutta] Notification request XML => 716722499715644344541786REN325App [08-Dec-2022 02:19:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:06 Asia/Calcutta] Notification request XML => 716722599715034456561786REN325App [08-Dec-2022 02:19:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:12 Asia/Calcutta] Notification request XML => 716722909715010030851786REN325App [08-Dec-2022 02:19:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:12 Asia/Calcutta] Notification request XML => 716722959715044292891786REN325App [08-Dec-2022 02:19:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:15 Asia/Calcutta] Notification request XML => 716723219715698033001786REN325App [08-Dec-2022 02:19:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:18 Asia/Calcutta] Notification request XML => 716723289715076557891786REN325App [08-Dec-2022 02:19:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:21 Asia/Calcutta] Notification request XML => 716723529715694322081786REN325App [08-Dec-2022 02:19:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:22 Asia/Calcutta] Notification request XML => 716723639715096085601786REN325App [08-Dec-2022 02:19:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:28 Asia/Calcutta] Notification request XML => 716724009715063227251786REN324App [08-Dec-2022 02:19:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:30 Asia/Calcutta] Notification request XML => 716724219715084312541786REN325App [08-Dec-2022 02:19:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:38 Asia/Calcutta] Notification request XML => 716724529715040039931786REN325App [08-Dec-2022 02:19:38 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:39 Asia/Calcutta] Notification request XML => 716724639715668396681786REN325App [08-Dec-2022 02:19:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:47 Asia/Calcutta] Notification request XML => 716724979715695096801786REN325App [08-Dec-2022 02:19:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:48 Asia/Calcutta] Notification request XML => 716725129715048104561786REN325App [08-Dec-2022 02:19:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:52 Asia/Calcutta] Notification request XML => 716725319715654654771786REN325App [08-Dec-2022 02:19:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:19:56 Asia/Calcutta] Notification request XML => 716725619715031379091786REN325App [08-Dec-2022 02:19:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:00 Asia/Calcutta] Notification request XML => 716726009715656315591786REN325App [08-Dec-2022 02:20:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:05 Asia/Calcutta] Notification request XML => 716726409715016735981786REN325App [08-Dec-2022 02:20:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:07 Asia/Calcutta] Notification request XML => 716726689715017486061786REN325App [08-Dec-2022 02:20:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:13 Asia/Calcutta] Notification request XML => 716727029715427600001786REN325App [08-Dec-2022 02:20:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:19 Asia/Calcutta] Notification request XML => 716727349715430115891786REN325App [08-Dec-2022 02:20:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:27 Asia/Calcutta] Notification request XML => 716727709715025921221786REN325App [08-Dec-2022 02:20:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:41 Asia/Calcutta] Notification request XML => 716728079715455389481786REN325App [08-Dec-2022 02:20:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:47 Asia/Calcutta] Notification request XML => 716728419715478199711786REN325App [08-Dec-2022 02:20:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:51 Asia/Calcutta] Notification request XML => 716728759715621406541786REN325App [08-Dec-2022 02:20:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:53 Asia/Calcutta] Notification request XML => 716728809715666307581786REN325App [08-Dec-2022 02:20:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:20:56 Asia/Calcutta] Notification request XML => 716729189715079636351786REN325App [08-Dec-2022 02:20:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:23 Asia/Calcutta] Notification request XML => 716729839715076405181786REN325App [08-Dec-2022 02:21:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:25 Asia/Calcutta] Notification request XML => 716729969715051961551786REN80App [08-Dec-2022 02:21:25 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:33 Asia/Calcutta] Notification request XML => 716730189715430068641786REN325App [08-Dec-2022 02:21:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:34 Asia/Calcutta] Notification request XML => 716730309715667788111786REN325App [08-Dec-2022 02:21:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:39 Asia/Calcutta] Notification request XML => 716730529715055994241786REN325App [08-Dec-2022 02:21:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:40 Asia/Calcutta] Notification request XML => 716730679715522414061786REN325App [08-Dec-2022 02:21:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:42 Asia/Calcutta] Notification request XML => 716730869715470199991786REN325App [08-Dec-2022 02:21:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:44 Asia/Calcutta] Notification request XML => 716731059715068897931786REN325App [08-Dec-2022 02:21:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:49 Asia/Calcutta] Notification request XML => 716731249715066816841786REN325App [08-Dec-2022 02:21:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:50 Asia/Calcutta] Notification request XML => 716731419715073666751786REN325App [08-Dec-2022 02:21:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:53 Asia/Calcutta] Notification request XML => 716731579715650360871786REN325App [08-Dec-2022 02:21:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:21:58 Asia/Calcutta] Notification request XML => 716731909715067849721786REN325App [08-Dec-2022 02:21:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:00 Asia/Calcutta] Notification request XML => 716732059715079719191786REN325App [08-Dec-2022 02:22:00 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:07 Asia/Calcutta] Notification request XML => 716732299715663355571786REN325App [08-Dec-2022 02:22:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:09 Asia/Calcutta] Notification request XML => 716732439715652668461786REN325App [08-Dec-2022 02:22:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:13 Asia/Calcutta] Notification request XML => 716732649715695195971786REN325App [08-Dec-2022 02:22:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:14 Asia/Calcutta] Notification request XML => 716732759715040396381786REN325App [08-Dec-2022 02:22:14 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:18 Asia/Calcutta] Notification request XML => 716733109715036736091786REN325App [08-Dec-2022 02:22:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:24 Asia/Calcutta] Notification request XML => 716733549715081078151786REN325App [08-Dec-2022 02:22:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:26 Asia/Calcutta] Notification request XML => 716733619715069494911786REN325App [08-Dec-2022 02:22:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:32 Asia/Calcutta] Notification request XML => 716733899715082292221786REN325App [08-Dec-2022 02:22:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:33 Asia/Calcutta] Notification request XML => 716734019715856732971786REN325App [08-Dec-2022 02:22:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:37 Asia/Calcutta] Notification request XML => 716734339715051371111786REN325App [08-Dec-2022 02:22:37 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:45 Asia/Calcutta] Notification request XML => 716734809715676761501786REN325App [08-Dec-2022 02:22:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:53 Asia/Calcutta] Notification request XML => 716735229715626146981786REN325App [08-Dec-2022 02:22:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:22:59 Asia/Calcutta] Notification request XML => 716735549715615354591786REN325App [08-Dec-2022 02:22:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:07 Asia/Calcutta] Notification request XML => 716735959715693141641786REN325App [08-Dec-2022 02:23:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:13 Asia/Calcutta] Notification request XML => 716736379715662534691786REN325App [08-Dec-2022 02:23:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:14 Asia/Calcutta] Notification request XML => 716736479715062767621786REN325App [08-Dec-2022 02:23:14 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:22 Asia/Calcutta] Notification request XML => 716736779715052925731786REN325App [08-Dec-2022 02:23:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:28 Asia/Calcutta] Notification request XML => 716737159715033350271786REN325App [08-Dec-2022 02:23:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:32 Asia/Calcutta] Notification request XML => 716737529715087087181786REN325App [08-Dec-2022 02:23:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:39 Asia/Calcutta] Notification request XML => 716737949715451085501786REN325App [08-Dec-2022 02:23:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:42 Asia/Calcutta] Notification request XML => 716738309715472017431786REN325App [08-Dec-2022 02:23:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:50 Asia/Calcutta] Notification request XML => 716738759715676312981786REN325App [08-Dec-2022 02:23:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:57 Asia/Calcutta] Notification request XML => 716739049715636994801786REN325App [08-Dec-2022 02:23:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:23:59 Asia/Calcutta] Notification request XML => 716739189715074898021786REN325App [08-Dec-2022 02:23:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:13 Asia/Calcutta] Notification request XML => 716739439715099494911786REN325App [08-Dec-2022 02:24:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:15 Asia/Calcutta] Notification request XML => 716739579715611391241786REN325App [08-Dec-2022 02:24:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:18 Asia/Calcutta] Notification request XML => 716739809715040951771786REN325App [08-Dec-2022 02:24:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:21 Asia/Calcutta] Notification request XML => 716739959715041495381786REN325App [08-Dec-2022 02:24:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:23 Asia/Calcutta] Notification request XML => 716740219715676990631786REN325App [08-Dec-2022 02:24:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:25 Asia/Calcutta] Notification request XML => 716740329715684373771786REN325App [08-Dec-2022 02:24:25 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:29 Asia/Calcutta] Notification request XML => 716740579715026225201786REN325App [08-Dec-2022 02:24:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:30 Asia/Calcutta] Notification request XML => 716740659715020376191786REN325App [08-Dec-2022 02:24:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:34 Asia/Calcutta] Notification request XML => 716741059715031673151786REN325App [08-Dec-2022 02:24:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:42 Asia/Calcutta] Notification request XML => 716741549715077132211786REN87App [08-Dec-2022 02:24:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:46 Asia/Calcutta] Notification request XML => 716741719715663495891786REN325App [08-Dec-2022 02:24:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:48 Asia/Calcutta] Notification request XML => 716741929715039395351786REN325App [08-Dec-2022 02:24:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:52 Asia/Calcutta] Notification request XML => 716742089715041675551786REN325App [08-Dec-2022 02:24:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:53 Asia/Calcutta] Notification request XML => 716742279715062231361786REN325App [08-Dec-2022 02:24:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:24:57 Asia/Calcutta] Notification request XML => 716742419715437734881786REN325App [08-Dec-2022 02:24:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:05 Asia/Calcutta] Notification request XML => 716742809715011366651786REN325App [08-Dec-2022 02:25:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:05 Asia/Calcutta] Notification request XML => 716742889715669966691786REN325App [08-Dec-2022 02:25:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:14 Asia/Calcutta] Notification request XML => 716743159715061108441786REN325App [08-Dec-2022 02:25:14 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:15 Asia/Calcutta] Notification request XML => 716743239715079591911786REN325App [08-Dec-2022 02:25:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:19 Asia/Calcutta] Notification request XML => 716743559715071999191786REN325App [08-Dec-2022 02:25:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:20 Asia/Calcutta] Notification request XML => 716743649715444350021786REN325App [08-Dec-2022 02:25:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:28 Asia/Calcutta] Notification request XML => 716743969715430912031786REN325App [08-Dec-2022 02:25:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:29 Asia/Calcutta] Notification request XML => 716744069715082931221786REN325App [08-Dec-2022 02:25:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:38 Asia/Calcutta] Notification request XML => 716744479715073784231786REN24App [08-Dec-2022 02:25:38 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:41 Asia/Calcutta] Notification request XML => 716744679715045678051786REN325App [08-Dec-2022 02:25:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:46 Asia/Calcutta] Notification request XML => 716745059715632024211786REN27App [08-Dec-2022 02:25:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:46 Asia/Calcutta] Notification request XML => 716745139715019016691786REN325App [08-Dec-2022 02:25:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:50 Asia/Calcutta] Notification request XML => 716745369715046646071786REN325App [08-Dec-2022 02:25:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:51 Asia/Calcutta] Notification request XML => 716745549715431751651786REN325App [08-Dec-2022 02:25:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:54 Asia/Calcutta] Notification request XML => 716745769715068609471786REN325App [08-Dec-2022 02:25:54 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:55 Asia/Calcutta] Notification request XML => 716745929715099402861786REN325App [08-Dec-2022 02:25:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:58 Asia/Calcutta] Notification request XML => 716746189715089343451786REN325App [08-Dec-2022 02:25:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:25:59 Asia/Calcutta] Notification request XML => 716746319715232725861786REN325App [08-Dec-2022 02:25:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:07 Asia/Calcutta] Notification request XML => 716746719715647274441786REN325App [08-Dec-2022 02:26:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:10 Asia/Calcutta] Notification request XML => 716746879715444972221786REN325App [08-Dec-2022 02:26:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:21 Asia/Calcutta] Notification request XML => 716747659715666637321786REN325App [08-Dec-2022 02:26:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:21 Asia/Calcutta] Notification request XML => 716747679715098007771786REN325App [08-Dec-2022 02:26:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:27 Asia/Calcutta] Notification request XML => 716748039715050488881786REN325App [08-Dec-2022 02:26:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:28 Asia/Calcutta] Notification request XML => 716748089715055861111786REN325App [08-Dec-2022 02:26:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:32 Asia/Calcutta] Notification request XML => 716748469715058093061786REN325App [08-Dec-2022 02:26:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:42 Asia/Calcutta] Notification request XML => 716748819715062963051786REN325App [08-Dec-2022 02:26:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:43 Asia/Calcutta] Notification request XML => 716748919715044573241786REN325App [08-Dec-2022 02:26:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:45 Asia/Calcutta] Notification request XML => 716749139715062621511786REN325App [08-Dec-2022 02:26:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:46 Asia/Calcutta] Notification request XML => 716749239715021133371786REN325App [08-Dec-2022 02:26:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:49 Asia/Calcutta] Notification request XML => 716749509715063303371786REN325App [08-Dec-2022 02:26:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:55 Asia/Calcutta] Notification request XML => 716749909715434443741786REN325App [08-Dec-2022 02:26:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:26:55 Asia/Calcutta] Notification request XML => 716749959715015370001786REN325App [08-Dec-2022 02:26:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:09 Asia/Calcutta] Notification request XML => 716750749715036273361786REN325App [08-Dec-2022 02:27:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:13 Asia/Calcutta] Notification request XML => 716750959715615482691786REN325App [08-Dec-2022 02:27:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:15 Asia/Calcutta] Notification request XML => 716751179715668030351786REN325App [08-Dec-2022 02:27:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:18 Asia/Calcutta] Notification request XML => 716751319715090271571786REN325App [08-Dec-2022 02:27:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:21 Asia/Calcutta] Notification request XML => 716751559715042102711786REN325App [08-Dec-2022 02:27:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:31 Asia/Calcutta] Notification request XML => 716752029715649577511786REN325App [08-Dec-2022 02:27:31 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:35 Asia/Calcutta] Notification request XML => 716752279715067659361786REN325App [08-Dec-2022 02:27:35 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:36 Asia/Calcutta] Notification request XML => 716752339715098356301786REN325App [08-Dec-2022 02:27:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:38 Asia/Calcutta] Notification request XML => 716752579715693601601786REN325App [08-Dec-2022 02:27:38 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:46 Asia/Calcutta] Notification request XML => 716752949715067060551786REN325App [08-Dec-2022 02:27:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:50 Asia/Calcutta] Notification request XML => 716753309715013357891786REN325App [08-Dec-2022 02:27:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:55 Asia/Calcutta] Notification request XML => 716753619715033741791786REN325App [08-Dec-2022 02:27:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:27:58 Asia/Calcutta] Notification request XML => 716753729715040002341786REN325App [08-Dec-2022 02:27:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:02 Asia/Calcutta] Notification request XML => 716753939715048121711786REN325App [08-Dec-2022 02:28:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:04 Asia/Calcutta] Notification request XML => 716754089715625764291786REN325App [08-Dec-2022 02:28:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:11 Asia/Calcutta] Notification request XML => 716754499715452993431786REN325App [08-Dec-2022 02:28:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:13 Asia/Calcutta] Notification request XML => 716754569715063298931786REN325App [08-Dec-2022 02:28:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:21 Asia/Calcutta] Notification request XML => 716754939715688834591786REN325App [08-Dec-2022 02:28:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:22 Asia/Calcutta] Notification request XML => 716754989715022777901786REN325App [08-Dec-2022 02:28:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:28 Asia/Calcutta] Notification request XML => 716755329715063397231786REN325App [08-Dec-2022 02:28:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:34 Asia/Calcutta] Notification request XML => 716755739715041212581786REN325App [08-Dec-2022 02:28:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:41 Asia/Calcutta] Notification request XML => 716756109715070122241786REN325App [08-Dec-2022 02:28:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:47 Asia/Calcutta] Notification request XML => 716756449715666667721786REN325App [08-Dec-2022 02:28:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:28:52 Asia/Calcutta] Notification request XML => 716756789715049292271786REN325App [08-Dec-2022 02:28:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:04 Asia/Calcutta] Notification request XML => 716757449715026307991786REN325App [08-Dec-2022 02:29:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:12 Asia/Calcutta] Notification request XML => 716757719715610111341786REN325App [08-Dec-2022 02:29:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:25 Asia/Calcutta] Notification request XML => 716758129715055012201786REN325App [08-Dec-2022 02:29:25 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:34 Asia/Calcutta] Notification request XML => 716758669715088707411786REN325App [08-Dec-2022 02:29:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:36 Asia/Calcutta] Notification request XML => 716758769715660945511786REN325App [08-Dec-2022 02:29:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:41 Asia/Calcutta] Notification request XML => 716759089715447505851786REN325App [08-Dec-2022 02:29:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:44 Asia/Calcutta] Notification request XML => 716759269715615673141786REN325App [08-Dec-2022 02:29:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:45 Asia/Calcutta] Notification request XML => 716759389715611621211786REN325App [08-Dec-2022 02:29:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:48 Asia/Calcutta] Notification request XML => 716759579715434445521786REN325App [08-Dec-2022 02:29:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:51 Asia/Calcutta] Notification request XML => 716759869715033194451786REN325App [08-Dec-2022 02:29:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:29:59 Asia/Calcutta] Notification request XML => 716760229715626769921786REN325App [08-Dec-2022 02:29:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:05 Asia/Calcutta] Notification request XML => 716760549715552741171786REN325App [08-Dec-2022 02:30:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:07 Asia/Calcutta] Notification request XML => 716760599715440599911786REN325App [08-Dec-2022 02:30:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:10 Asia/Calcutta] Notification request XML => 716760899715034004021786REN325App [08-Dec-2022 02:30:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:13 Asia/Calcutta] Notification request XML => 716760989715077128361786REN325App [08-Dec-2022 02:30:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:20 Asia/Calcutta] Notification request XML => 716761349715614048001786REN325App [08-Dec-2022 02:30:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:26 Asia/Calcutta] Notification request XML => 716761559715648317251786REN325App [08-Dec-2022 02:30:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:34 Asia/Calcutta] Notification request XML => 716761979715030945421786REN325App [08-Dec-2022 02:30:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:42 Asia/Calcutta] Notification request XML => 716762349715023125001786REN325App [08-Dec-2022 02:30:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:44 Asia/Calcutta] Notification request XML => 716762649715655080001786REN325App [08-Dec-2022 02:30:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:53 Asia/Calcutta] Notification request XML => 716763009715098544011786REN325App [08-Dec-2022 02:30:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:30:57 Asia/Calcutta] Notification request XML => 716763349715099331831786REN325App [08-Dec-2022 02:30:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:04 Asia/Calcutta] Notification request XML => 716763679715063800511786REN325App [08-Dec-2022 02:31:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:07 Asia/Calcutta] Notification request XML => 716763859715069449781786REN325App [08-Dec-2022 02:31:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:07 Asia/Calcutta] Notification request XML => 716763929715457780191786REN325App [08-Dec-2022 02:31:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:19 Asia/Calcutta] Notification request XML => 716764169715694133601786REN325App [08-Dec-2022 02:31:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:26 Asia/Calcutta] Notification request XML => 716764499715473898611786REN325App [08-Dec-2022 02:31:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:26 Asia/Calcutta] Notification request XML => 716764519715071113581786REN325App [08-Dec-2022 02:31:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:34 Asia/Calcutta] Notification request XML => 716764769715437114541786REN325App [08-Dec-2022 02:31:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:37 Asia/Calcutta] Notification request XML => 716765009715596619691786REN325App [08-Dec-2022 02:31:37 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:41 Asia/Calcutta] Notification request XML => 716765369715650059721786REN325App [08-Dec-2022 02:31:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:49 Asia/Calcutta] Notification request XML => 716765759715010116511786REN325App [08-Dec-2022 02:31:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:55 Asia/Calcutta] Notification request XML => 716766019715660110001786REN325App [08-Dec-2022 02:31:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:31:55 Asia/Calcutta] Notification request XML => 716766129715079147331786REN325App [08-Dec-2022 02:31:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:03 Asia/Calcutta] Notification request XML => 716766429715474348281786REN325App [08-Dec-2022 02:32:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:09 Asia/Calcutta] Notification request XML => 716766609715079042241786REN325App [08-Dec-2022 02:32:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:10 Asia/Calcutta] Notification request XML => 716766749715693121191786REN325App [08-Dec-2022 02:32:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:15 Asia/Calcutta] Notification request XML => 716767069715674525131786REN325App [08-Dec-2022 02:32:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:17 Asia/Calcutta] Notification request XML => 716767159715431998821786REN325App [08-Dec-2022 02:32:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:25 Asia/Calcutta] Notification request XML => 716767729715070033781786REN325App [08-Dec-2022 02:32:25 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:33 Asia/Calcutta] Notification request XML => 716768119715458464251786REN325App [08-Dec-2022 02:32:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:44 Asia/Calcutta] Notification request XML => 716768809715697551191786REN325App [08-Dec-2022 02:32:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:50 Asia/Calcutta] Notification request XML => 716769149715632366741786REN179App [08-Dec-2022 02:32:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:32:57 Asia/Calcutta] Notification request XML => 716769539715080745761786REN325App [08-Dec-2022 02:32:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:04 Asia/Calcutta] Notification request XML => 716769949715629276111786REN325App [08-Dec-2022 02:33:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:05 Asia/Calcutta] Notification request XML => 716770019715044465151786REN325App [08-Dec-2022 02:33:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:20 Asia/Calcutta] Notification request XML => 716770849715098288751786REN325App [08-Dec-2022 02:33:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:31 Asia/Calcutta] Notification request XML => 716771239715439209851786REN325App [08-Dec-2022 02:33:31 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:38 Asia/Calcutta] Notification request XML => 716771629715477866671786REN325App [08-Dec-2022 02:33:38 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:45 Asia/Calcutta] Notification request XML => 716771969715034294801786REN325App [08-Dec-2022 02:33:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:33:57 Asia/Calcutta] Notification request XML => 716772529715061986601786REN325App [08-Dec-2022 02:33:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:34:07 Asia/Calcutta] Notification request XML => 716772699715558677761786REN325App [08-Dec-2022 02:34:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:34:10 Asia/Calcutta] Notification request XML => 716772859715440619751786REN325App [08-Dec-2022 02:34:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:34:17 Asia/Calcutta] Notification request XML => 716773109715437285401786REN325App [08-Dec-2022 02:34:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:34:19 Asia/Calcutta] Notification request XML => 716773259715056553451786REN325App [08-Dec-2022 02:34:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:34:32 Asia/Calcutta] Notification request XML => 716773639715659839161786REN325App [08-Dec-2022 02:34:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:34:46 Asia/Calcutta] Notification request XML => 716773949715072892331786REN325App [08-Dec-2022 02:34:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:35:10 Asia/Calcutta] Notification request XML => 716774279715024822931786REN325App [08-Dec-2022 02:35:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:35:42 Asia/Calcutta] Notification request XML => 716774849715093805001786REN325App [08-Dec-2022 02:35:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:35:50 Asia/Calcutta] Notification request XML => 716775129715014227031786REN325App [08-Dec-2022 02:35:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:35:59 Asia/Calcutta] Notification request XML => 716775449715011145241786REN325App [08-Dec-2022 02:35:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:05 Asia/Calcutta] Notification request XML => 716775839715072211781786REN325App [08-Dec-2022 02:36:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:12 Asia/Calcutta] Notification request XML => 716776199715681267311786REN325App [08-Dec-2022 02:36:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:16 Asia/Calcutta] Notification request XML => 716776349715035996111786REN325App [08-Dec-2022 02:36:16 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:23 Asia/Calcutta] Notification request XML => 716776549715639598821786REN325App [08-Dec-2022 02:36:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:24 Asia/Calcutta] Notification request XML => 716776659715057279621786REN325App [08-Dec-2022 02:36:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:33 Asia/Calcutta] Notification request XML => 716776939715014555961786REN325App [08-Dec-2022 02:36:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:34 Asia/Calcutta] Notification request XML => 716777019715456500221786REN325App [08-Dec-2022 02:36:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:48 Asia/Calcutta] Notification request XML => 716777419715073017131786REN26App [08-Dec-2022 02:36:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:36:55 Asia/Calcutta] Notification request XML => 716777579715044323761786REN325App [08-Dec-2022 02:36:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:37:03 Asia/Calcutta] Notification request XML => 716777809715077443371786REN325App [08-Dec-2022 02:37:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:37:10 Asia/Calcutta] Notification request XML => 716778129715689984631786REN325App [08-Dec-2022 02:37:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:37:24 Asia/Calcutta] Notification request XML => 716778569715019899351786REN325App [08-Dec-2022 02:37:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:37:24 Asia/Calcutta] Notification request XML => 716778589715666521141786REN325App [08-Dec-2022 02:37:25 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:37:32 Asia/Calcutta] Notification request XML => 716778949715064618721786REN140App [08-Dec-2022 02:37:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:37:59 Asia/Calcutta] Notification request XML => 716779989715676801111786REN325App [08-Dec-2022 02:37:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:07 Asia/Calcutta] Notification request XML => 716780349715645105261786REN139App [08-Dec-2022 02:38:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:21 Asia/Calcutta] Notification request XML => 716780629715065209201786REN325App [08-Dec-2022 02:38:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:26 Asia/Calcutta] Notification request XML => 716780909715054339961786REN325App [08-Dec-2022 02:38:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:29 Asia/Calcutta] Notification request XML => 716781149715629625451786REN325App [08-Dec-2022 02:38:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:36 Asia/Calcutta] Notification request XML => 716781529715684496091786REN285App [08-Dec-2022 02:38:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:38 Asia/Calcutta] Notification request XML => 716781769715049613991786REN325App [08-Dec-2022 02:38:38 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:41 Asia/Calcutta] Notification request XML => 716781859715031161671786REN325App [08-Dec-2022 02:38:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:43 Asia/Calcutta] Notification request XML => 716782079715045372661786REN325App [08-Dec-2022 02:38:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:44 Asia/Calcutta] Notification request XML => 716782149715655253551786REN325App [08-Dec-2022 02:38:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:51 Asia/Calcutta] Notification request XML => 716782389715050015011786REN325App [08-Dec-2022 02:38:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:52 Asia/Calcutta] Notification request XML => 716782479715084841901786REN325App [08-Dec-2022 02:38:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:58 Asia/Calcutta] Notification request XML => 716782689715617423671786REN325App [08-Dec-2022 02:38:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:38:58 Asia/Calcutta] Notification request XML => 716782779715096299631786REN325App [08-Dec-2022 02:38:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:08 Asia/Calcutta] Notification request XML => 716783029715051666011786REN325App [08-Dec-2022 02:39:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:11 Asia/Calcutta] Notification request XML => 716783129715457230051786REN325App [08-Dec-2022 02:39:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:27 Asia/Calcutta] Notification request XML => 716783349715474443881786REN325App [08-Dec-2022 02:39:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:28 Asia/Calcutta] Notification request XML => 716783459715455380841786REN325App [08-Dec-2022 02:39:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:35 Asia/Calcutta] Notification request XML => 716783659715431804001786REN325App [08-Dec-2022 02:39:35 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:43 Asia/Calcutta] Notification request XML => 716784009715471069501786REN325App [08-Dec-2022 02:39:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:43 Asia/Calcutta] Notification request XML => 716784059715684718881786REN325App [08-Dec-2022 02:39:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:54 Asia/Calcutta] Notification request XML => 716784339715451311311786REN325App [08-Dec-2022 02:39:54 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:39:55 Asia/Calcutta] Notification request XML => 716784399715434719331786REN325App [08-Dec-2022 02:39:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:02 Asia/Calcutta] Notification request XML => 716784619715635386561786REN325App [08-Dec-2022 02:40:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:04 Asia/Calcutta] Notification request XML => 716784709715077111811786REN325App [08-Dec-2022 02:40:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:11 Asia/Calcutta] Notification request XML => 716784959715645574991786REN325App [08-Dec-2022 02:40:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:12 Asia/Calcutta] Notification request XML => 716785059715045316781786REN325App [08-Dec-2022 02:40:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:27 Asia/Calcutta] Notification request XML => 716785429715665542701786REN325App [08-Dec-2022 02:40:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:38 Asia/Calcutta] Notification request XML => 716786069715097124721786REN325App [08-Dec-2022 02:40:38 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:44 Asia/Calcutta] Notification request XML => 716786459715013644931786REN325App [08-Dec-2022 02:40:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:40:52 Asia/Calcutta] Notification request XML => 716786799715012085621786REN325App [08-Dec-2022 02:40:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:05 Asia/Calcutta] Notification request XML => 716787219715449501691786REN325App [08-Dec-2022 02:41:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:05 Asia/Calcutta] Notification request XML => 716787269715542300021786REN325App [08-Dec-2022 02:41:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:12 Asia/Calcutta] Notification request XML => 716787669715035622151786REN325App [08-Dec-2022 02:41:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:15 Asia/Calcutta] Notification request XML => 716787899715093588081786REN325App [08-Dec-2022 02:41:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:19 Asia/Calcutta] Notification request XML => 716788009715039113011786REN325App [08-Dec-2022 02:41:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:22 Asia/Calcutta] Notification request XML => 716788249715061748581786REN325App [08-Dec-2022 02:41:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:26 Asia/Calcutta] Notification request XML => 716788369715023382971786REN325App [08-Dec-2022 02:41:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:35 Asia/Calcutta] Notification request XML => 716788629715011415151786REN325App [08-Dec-2022 02:41:35 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:42 Asia/Calcutta] Notification request XML => 716788939715068198141786REN325App [08-Dec-2022 02:41:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:48 Asia/Calcutta] Notification request XML => 716789269715653043631786REN325App [08-Dec-2022 02:41:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:41:59 Asia/Calcutta] Notification request XML => 716789589715055313201786REN325App [08-Dec-2022 02:41:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:05 Asia/Calcutta] Notification request XML => 716789879715057493391786REN325App [08-Dec-2022 02:42:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:11 Asia/Calcutta] Notification request XML => 716790239715633572751786REN325App [08-Dec-2022 02:42:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:22 Asia/Calcutta] Notification request XML => 716790639715042031521786REN325App [08-Dec-2022 02:42:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:36 Asia/Calcutta] Notification request XML => 716791259715067084211786REN325App [08-Dec-2022 02:42:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:44 Asia/Calcutta] Notification request XML => 716791689715685809021786REN325App [08-Dec-2022 02:42:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:53 Asia/Calcutta] Notification request XML => 716791979715631423591786REN325App [08-Dec-2022 02:42:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:42:56 Asia/Calcutta] Notification request XML => 716792319715698625751786REN325App [08-Dec-2022 02:42:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:43:08 Asia/Calcutta] Notification request XML => 716792649715645809011786REN100App [08-Dec-2022 02:43:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:43:18 Asia/Calcutta] Notification request XML => 716793109715676982351786REN325App [08-Dec-2022 02:43:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:43:28 Asia/Calcutta] Notification request XML => 716793329715022593091786REN325App [08-Dec-2022 02:43:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:43:37 Asia/Calcutta] Notification request XML => 716793699715678547861786REN325App [08-Dec-2022 02:43:37 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:44:02 Asia/Calcutta] Notification request XML => 716794409715472791741786REN325App [08-Dec-2022 02:44:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:44:07 Asia/Calcutta] Notification request XML => 716794679715624790951786REN87App [08-Dec-2022 02:44:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:44:35 Asia/Calcutta] Notification request XML => 716795399715653130261786REN155App [08-Dec-2022 02:44:35 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:44:55 Asia/Calcutta] Notification request XML => 716796169715447944961786REN325App [08-Dec-2022 02:44:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:45:09 Asia/Calcutta] Notification request XML => 716797309715695560131786REN325App [08-Dec-2022 02:45:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:45:27 Asia/Calcutta] Notification request XML => 716797909715443046101786REN325App [08-Dec-2022 02:45:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:45:57 Asia/Calcutta] Notification request XML => 716798919715656812291786REN325App [08-Dec-2022 02:45:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:46:04 Asia/Calcutta] Notification request XML => 716799329715077485181786REN161App [08-Dec-2022 02:46:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:46:30 Asia/Calcutta] Notification request XML => 716800349715057261151786REN325App [08-Dec-2022 02:46:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:46:45 Asia/Calcutta] Notification request XML => 716800699715685585841786REN325App [08-Dec-2022 02:46:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:46:50 Asia/Calcutta] Notification request XML => 716801049715658589441786REN325App [08-Dec-2022 02:46:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:47:01 Asia/Calcutta] Notification request XML => 716801759715618597141786REN325App [08-Dec-2022 02:47:01 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:47:21 Asia/Calcutta] Notification request XML => 716802849715022072271786REN325App [08-Dec-2022 02:47:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:47:26 Asia/Calcutta] Notification request XML => 716802959715631141221786REN325App [08-Dec-2022 02:47:26 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:47:36 Asia/Calcutta] Notification request XML => 716803369715079703231786REN325App [08-Dec-2022 02:47:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:47:40 Asia/Calcutta] Notification request XML => 716803749715632759221786REN300App [08-Dec-2022 02:47:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:47:55 Asia/Calcutta] Notification request XML => 716804449715676919051786REN158App [08-Dec-2022 02:47:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:48:03 Asia/Calcutta] Notification request XML => 716804859715627710441786REN228App [08-Dec-2022 02:48:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:48:17 Asia/Calcutta] Notification request XML => 716805579715662686201786REN52App [08-Dec-2022 02:48:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:48:23 Asia/Calcutta] Notification request XML => 716805959715024681831786REN304App [08-Dec-2022 02:48:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:48:33 Asia/Calcutta] Notification request XML => 716806309715053292821786REN325App [08-Dec-2022 02:48:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:48:51 Asia/Calcutta] Notification request XML => 716807019715642154841786REN325App [08-Dec-2022 02:48:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:49:04 Asia/Calcutta] Notification request XML => 716807219715653156501786REN137App [08-Dec-2022 02:49:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:49:11 Asia/Calcutta] Notification request XML => 716807519715471799931786REN325App [08-Dec-2022 02:49:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:49:18 Asia/Calcutta] Notification request XML => 716807859715449145231786REN73App [08-Dec-2022 02:49:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:49:29 Asia/Calcutta] Notification request XML => 716808249715034567971786REN325App [08-Dec-2022 02:49:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:49:41 Asia/Calcutta] Notification request XML => 716808879715099546601786REN159App [08-Dec-2022 02:49:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:04 Asia/Calcutta] Notification request XML => 716809249715031585591786REN225App [08-Dec-2022 02:50:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:11 Asia/Calcutta] Notification request XML => 716809779715457355161786REN149App [08-Dec-2022 02:50:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:12 Asia/Calcutta] Notification request XML => 716809899715045970851786REN16App [08-Dec-2022 02:50:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:18 Asia/Calcutta] Notification request XML => 716810269715472366341786REN15App [08-Dec-2022 02:50:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:19 Asia/Calcutta] Notification request XML => 716810359715623714231786REN325App [08-Dec-2022 02:50:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:42 Asia/Calcutta] Notification request XML => 716810879715054924701786REN325App [08-Dec-2022 02:50:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:50:56 Asia/Calcutta] Notification request XML => 716811209715674187871786REN325App [08-Dec-2022 02:50:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:51:20 Asia/Calcutta] Notification request XML => 716811939715055509361786REN175App [08-Dec-2022 02:51:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:51:47 Asia/Calcutta] Notification request XML => 716812689715059606361786REN325App [08-Dec-2022 02:51:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:51:51 Asia/Calcutta] Notification request XML => 716812999715045143091786REN325App [08-Dec-2022 02:51:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:51:57 Asia/Calcutta] Notification request XML => 716813389715696756911786REN255App [08-Dec-2022 02:51:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:06 Asia/Calcutta] Notification request XML => 716813809715458590651786REN325App [08-Dec-2022 02:52:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:10 Asia/Calcutta] Notification request XML => 716814199715445241691786REN325App [08-Dec-2022 02:52:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:12 Asia/Calcutta] Notification request XML => 716814309715024963741786REN65App [08-Dec-2022 02:52:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:20 Asia/Calcutta] Notification request XML => 716814619715479068151786REN325App [08-Dec-2022 02:52:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:33 Asia/Calcutta] Notification request XML => 716814989715082877861786REN163App [08-Dec-2022 02:52:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:40 Asia/Calcutta] Notification request XML => 716815329715027797951786REN325App [08-Dec-2022 02:52:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:46 Asia/Calcutta] Notification request XML => 716815669715523880111786REN325App [08-Dec-2022 02:52:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:52:49 Asia/Calcutta] Notification request XML => 716816049715449377401786REN325App [08-Dec-2022 02:52:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:53:17 Asia/Calcutta] Notification request XML => 716817129715690692591786REN325App [08-Dec-2022 02:53:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:53:30 Asia/Calcutta] Notification request XML => 716817519715613847891786REN325App [08-Dec-2022 02:53:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:53:50 Asia/Calcutta] Notification request XML => 716818319715433509811786REN325App [08-Dec-2022 02:53:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:53:52 Asia/Calcutta] Notification request XML => 716818689715675882451786REN142App [08-Dec-2022 02:53:52 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:54:01 Asia/Calcutta] Notification request XML => 716818999715075932521786REN325App [08-Dec-2022 02:54:01 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:54:04 Asia/Calcutta] Notification request XML => 716819239715432549751786REN325App [08-Dec-2022 02:54:04 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:54:40 Asia/Calcutta] Notification request XML => 716819999715084188931786REN325App [08-Dec-2022 02:54:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:54:46 Asia/Calcutta] Notification request XML => 716820339715452221371786REN325App [08-Dec-2022 02:54:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:54:49 Asia/Calcutta] Notification request XML => 716820559715054149541786REN325App [08-Dec-2022 02:54:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:55:10 Asia/Calcutta] Notification request XML => 716821779715664485721786REN325App [08-Dec-2022 02:55:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:55:27 Asia/Calcutta] Notification request XML => 716822169715671837241786REN325App [08-Dec-2022 02:55:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:55:56 Asia/Calcutta] Notification request XML => 716823559715018248061786REN325App [08-Dec-2022 02:55:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:08 Asia/Calcutta] Notification request XML => 716823899715680690451786REN325App [08-Dec-2022 02:56:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:17 Asia/Calcutta] Notification request XML => 716824019715694824971786REN325App [08-Dec-2022 02:56:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:21 Asia/Calcutta] Notification request XML => 716824249715691008841786REN325App [08-Dec-2022 02:56:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:33 Asia/Calcutta] Notification request XML => 716824569715091535401786REN175App [08-Dec-2022 02:56:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:45 Asia/Calcutta] Notification request XML => 716825289715078651831786REN325App [08-Dec-2022 02:56:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:51 Asia/Calcutta] Notification request XML => 716825659715438581501786REN276App [08-Dec-2022 02:56:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:56 Asia/Calcutta] Notification request XML => 716825959715085892221786REN325App [08-Dec-2022 02:56:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:56:59 Asia/Calcutta] Notification request XML => 716826269715687942351786REN325App [08-Dec-2022 02:56:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:02 Asia/Calcutta] Notification request XML => 716826629715633703711786REN290App [08-Dec-2022 02:57:02 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:11 Asia/Calcutta] Notification request XML => 716826959715050472651786REN325App [08-Dec-2022 02:57:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:15 Asia/Calcutta] Notification request XML => 716827279715685656211786REN325App [08-Dec-2022 02:57:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:21 Asia/Calcutta] Notification request XML => 716827599715097725631786REN256App [08-Dec-2022 02:57:21 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:24 Asia/Calcutta] Notification request XML => 716827779715449714661786REN325App [08-Dec-2022 02:57:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:35 Asia/Calcutta] Notification request XML => 716828099715082576551786REN323App [08-Dec-2022 02:57:35 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:37 Asia/Calcutta] Notification request XML => 716828379715628435501786REN185App [08-Dec-2022 02:57:37 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:57:42 Asia/Calcutta] Notification request XML => 716828719715654215691786REN176App [08-Dec-2022 02:57:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:59:40 Asia/Calcutta] Notification request XML => 716835909715665411501786REN325App [08-Dec-2022 02:59:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 02:59:43 Asia/Calcutta] Notification request XML => 717153951670448533338c316984c19715432931151786SUB00App [08-Dec-2022 02:59:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 03:46:07 Asia/Calcutta] Notification request XML => 717672491670451332996c317018c19715085693171786SUB00App [08-Dec-2022 03:46:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 04:36:48 Asia/Calcutta] Notification request XML => 3730701209715085120171786UNSUBG325App [08-Dec-2022 04:36:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 04:48:39 Asia/Calcutta] Notification request XML => [08-Dec-2022 04:48:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 05:38:24 Asia/Calcutta] Notification request XML => 718589981670458071261c317036c19715679883111786SUB00App [08-Dec-2022 05:38:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 05:40:49 Asia/Calcutta] Notification request XML => 718590411670458171193c317038c19715073328781786SUB00App [08-Dec-2022 05:40:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 05:43:10 Asia/Calcutta] Notification request XML => [08-Dec-2022 05:43:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 06:48:22 Asia/Calcutta] Notification request XML => 718595901670462264263c317044c19715035094651786SUB00App [08-Dec-2022 06:48:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 06:57:47 Asia/Calcutta] Notification request XML => 713851829715016469871786UNSUB1750Ccare [08-Dec-2022 06:57:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 07:57:10 Asia/Calcutta] Notification request XML => 716431879715698015881786UNSUB3250App [08-Dec-2022 07:57:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:08:43 Asia/Calcutta] Notification request XML => 718106069715096278091786REN64App [08-Dec-2022 09:08:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:08:44 Asia/Calcutta] Notification request XML => 718106479715647735761786REN325App [08-Dec-2022 09:08:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:08:44 Asia/Calcutta] Notification request XML => 718106709715050546411786REN325App [08-Dec-2022 09:08:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:08:44 Asia/Calcutta] Notification request XML => 718107299715568080301786REN192App [08-Dec-2022 09:08:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:08:45 Asia/Calcutta] Notification request XML => 718109209715662637921786REN325App [08-Dec-2022 09:08:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:08:45 Asia/Calcutta] Notification request XML => 718109529715429799371786REN325App [08-Dec-2022 09:08:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:25:03 Asia/Calcutta] Notification request XML => 718590829715054056781786REN325App [08-Dec-2022 09:25:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:27:03 Asia/Calcutta] Notification request XML => 718597129715680890751786REN325App [08-Dec-2022 09:27:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:28:46 Asia/Calcutta] Notification request XML => 718604059715680585681786REN152App [08-Dec-2022 09:28:46 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:29:12 Asia/Calcutta] Notification request XML => 718605669715058096711786REN325App [08-Dec-2022 09:29:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:30:03 Asia/Calcutta] Notification request XML => 718608389715043522851786REN325App [08-Dec-2022 09:30:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:32:39 Asia/Calcutta] Notification request XML => 718611969715451641681786REN325App [08-Dec-2022 09:32:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:33:56 Asia/Calcutta] Notification request XML => 718613349715473414581786REN325App [08-Dec-2022 09:33:56 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 09:43:39 Asia/Calcutta] Notification request XML => 718622889715074612981786REN325App [08-Dec-2022 09:43:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 10:23:29 Asia/Calcutta] Notification request XML => 718832619715093104471786REN325App [08-Dec-2022 10:23:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 10:35:28 Asia/Calcutta] Notification request XML => 718893139715068050981786REN114App [08-Dec-2022 10:35:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 10:35:29 Asia/Calcutta] Notification request XML => 718893349715078872211786REN325App [08-Dec-2022 10:35:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 10:35:29 Asia/Calcutta] Notification request XML => 718893609715012814131786REN325App [08-Dec-2022 10:35:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 10:35:29 Asia/Calcutta] Notification request XML => 718893859715436785391786REN325App [08-Dec-2022 10:35:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 10:41:47 Asia/Calcutta] Notification request XML => 718910929715457482021786REN325App [08-Dec-2022 10:41:47 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 11:09:30 Asia/Calcutta] Notification request XML => 718976299715690685621786REN325App [08-Dec-2022 11:09:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 11:43:28 Asia/Calcutta] Notification request XML => 719215659715017083381786REN325App [08-Dec-2022 11:43:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 11:49:24 Asia/Calcutta] Notification request XML => 719255089715028854011786REN200App [08-Dec-2022 11:49:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 11:57:18 Asia/Calcutta] Notification request XML => 719274669715452936721786REN325App [08-Dec-2022 11:57:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:03:17 Asia/Calcutta] Notification request XML => 719276159715436229321786REN184App [08-Dec-2022 12:03:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:05:11 Asia/Calcutta] Notification request XML => 719276659715626296371786REN80App [08-Dec-2022 12:05:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:19:12 Asia/Calcutta] Notification request XML => 719280829715450135391786REN325App [08-Dec-2022 12:19:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:39:24 Asia/Calcutta] Notification request XML => 719287089715079138151786REN325App [08-Dec-2022 12:39:24 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:41:27 Asia/Calcutta] Notification request XML => 719287739715475401641786REN325App [08-Dec-2022 12:41:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:51:08 Asia/Calcutta] Notification request XML => 719290779715664787971786REN325App [08-Dec-2022 12:51:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:51:59 Asia/Calcutta] Notification request XML => 654163359715457233721786UNSUB1750cease [08-Dec-2022 12:51:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 12:53:12 Asia/Calcutta] Notification request XML => 719291369715629472731786REN325App [08-Dec-2022 12:53:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:07:25 Asia/Calcutta] Notification request XML => 719297739715689383761786REN325App [08-Dec-2022 13:07:25 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:18:58 Asia/Calcutta] Notification request XML => 719303419715438220581786REN161App [08-Dec-2022 13:18:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:18:58 Asia/Calcutta] Notification request XML => 719303429715614733181786REN306App [08-Dec-2022 13:18:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:18:58 Asia/Calcutta] Notification request XML => 716733109715036736091786UNSUB00Ccare [08-Dec-2022 13:18:58 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:18:59 Asia/Calcutta] Notification request XML => 719303439715625575031786REN325App [08-Dec-2022 13:18:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:18:59 Asia/Calcutta] Notification request XML => 719303449715427362641786REN37App [08-Dec-2022 13:18:59 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:25:13 Asia/Calcutta] Notification request XML => 719305699715434119051786REN325App [08-Dec-2022 13:25:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:27:01 Asia/Calcutta] Notification request XML => 719306229715443668361786REN325App [08-Dec-2022 13:27:01 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 13:29:29 Asia/Calcutta] Notification request XML => 719306819715091841371786REN325App [08-Dec-2022 13:29:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 14:21:08 Asia/Calcutta] Notification request XML => 719326519715010095641786REN325App [08-Dec-2022 14:21:08 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 14:23:09 Asia/Calcutta] Notification request XML => 692443579715438677121786UNSUB780Ccare [08-Dec-2022 14:23:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 14:23:22 Asia/Calcutta] Notification request XML => 719328109715686883121786REN325App [08-Dec-2022 14:23:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 14:27:03 Asia/Calcutta] Notification request XML => 719329789715689661101786REN142App [08-Dec-2022 14:27:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 15:17:28 Asia/Calcutta] Notification request XML => 719350131670492724351c317050c19715691913191786SUB00App [08-Dec-2022 15:17:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 15:19:17 Asia/Calcutta] Notification request XML => 719351029715439738791786REN325App [08-Dec-2022 15:19:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 15:21:17 Asia/Calcutta] Notification request XML => 719351509715084123521786REN325App [08-Dec-2022 15:21:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 15:41:27 Asia/Calcutta] Notification request XML => 719357079715663849161786REN325App [08-Dec-2022 15:41:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 15:43:14 Asia/Calcutta] Notification request XML => 719357699715456048641786REN155App [08-Dec-2022 15:43:14 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 16:05:07 Asia/Calcutta] Notification request XML => 719364919715071551071786REN325App [08-Dec-2022 16:05:07 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 16:47:20 Asia/Calcutta] Notification request XML => 719379949715433371491786REN325App [08-Dec-2022 16:47:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 16:53:29 Asia/Calcutta] Notification request XML => 719381499715098869341786REN325App [08-Dec-2022 16:53:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:15:06 Asia/Calcutta] Notification request XML => 719389509715031748941786REN325App [08-Dec-2022 17:15:06 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:25:51 Asia/Calcutta] Notification request XML => 713386269715089080581786UNSUB3250Ccare [08-Dec-2022 17:25:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:29:11 Asia/Calcutta] Notification request XML => 719394279715475875641786REN165App [08-Dec-2022 17:29:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:33:29 Asia/Calcutta] Notification request XML => 719395179715612697401786REN325App [08-Dec-2022 17:33:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:40:37 Asia/Calcutta] Notification request XML => 719397131670501362446c317089c19715613624841786SUB00App [08-Dec-2022 17:40:37 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:46:05 Asia/Calcutta] Notification request XML => 719399229715086303731786REN325App [08-Dec-2022 17:46:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:46:05 Asia/Calcutta] Notification request XML => 719399259715525741741786REN325App [08-Dec-2022 17:46:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:46:41 Asia/Calcutta] Notification request XML => 719399359715097979561786REN325App [08-Dec-2022 17:46:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:51:16 Asia/Calcutta] Notification request XML => 719401559715659928621786REN325App [08-Dec-2022 17:51:16 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 17:54:32 Asia/Calcutta] Notification request XML => 718893349715078872211786UNSUB3250Ccare [08-Dec-2022 17:54:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:01:45 Asia/Calcutta] Notification request XML => 719405849715673534871786REN325App [08-Dec-2022 18:01:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:05:17 Asia/Calcutta] Notification request XML => 719407361670502782597c317096c19715628171661786SUB00App [08-Dec-2022 18:05:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:07:31 Asia/Calcutta] Notification request XML => 719408329715621545001786REN325App [08-Dec-2022 18:07:31 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:11:27 Asia/Calcutta] Notification request XML => 574120679715635782001786UNSUB1330Ccare [08-Dec-2022 18:11:27 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:25:29 Asia/Calcutta] Notification request XML => 719419029715053162351786REN83App [08-Dec-2022 18:25:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:25:29 Asia/Calcutta] Notification request XML => 719419039715684225431786REN325App [08-Dec-2022 18:25:29 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:25:30 Asia/Calcutta] Notification request XML => 719419049715683290211786REN129App [08-Dec-2022 18:25:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:28:13 Asia/Calcutta] Notification request XML => 719419811670504212040c317108c19715629557651786SUB00App [08-Dec-2022 18:28:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:29:11 Asia/Calcutta] Notification request XML => 719420329715010049161786REN325App [08-Dec-2022 18:29:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:30:55 Asia/Calcutta] Notification request XML => 719420781670504302637c317110c19715694769041786SUB00App [08-Dec-2022 18:30:55 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:33:09 Asia/Calcutta] Notification request XML => 719421489715478051971786REN325App [08-Dec-2022 18:33:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:37:11 Asia/Calcutta] Notification request XML => 719422679715678867851786REN325App [08-Dec-2022 18:37:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 18:40:50 Asia/Calcutta] Notification request XML => 719423691670504960376c317118c19715620930291786SUB00App [08-Dec-2022 18:40:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:03:43 Asia/Calcutta] Notification request XML => 719431999715036832431786REN325App [08-Dec-2022 19:03:43 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:06:17 Asia/Calcutta] Notification request XML => 719433471670506490655c317134c19715015042031786SUB00App [08-Dec-2022 19:06:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:22:33 Asia/Calcutta] Notification request XML => 719443481670507444699c317146c19715034926101786SUB00App [08-Dec-2022 19:22:33 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:23:23 Asia/Calcutta] Notification request XML => 669902519715022823041786UNSUB00Ccare [08-Dec-2022 19:23:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:33:18 Asia/Calcutta] Notification request XML => 719448339715615396361786REN325App [08-Dec-2022 19:33:18 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:39:22 Asia/Calcutta] Notification request XML => 719450809715435722191786REN259App [08-Dec-2022 19:39:22 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 19:58:44 Asia/Calcutta] Notification request XML => 719458961670509672942c317165c19715015534891786SUB00App [08-Dec-2022 19:58:44 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:01:28 Asia/Calcutta] Notification request XML => 719460429715638287421786REN325App [08-Dec-2022 20:01:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:03:30 Asia/Calcutta] Notification request XML => 719461999715691360831786REN325App [08-Dec-2022 20:03:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:07:03 Asia/Calcutta] Notification request XML => 719463831670510134862c317173c19715655785921786SUB00App [08-Dec-2022 20:07:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:09:14 Asia/Calcutta] Notification request XML => 719419049715683290211786UNSUB1290App [08-Dec-2022 20:09:14 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:10:12 Asia/Calcutta] Notification request XML => 719466201670510309795c317180c19715646098271786SUB00App [08-Dec-2022 20:10:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:21:20 Asia/Calcutta] Notification request XML => 719473809715075848881786REN325App [08-Dec-2022 20:21:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:21:23 Asia/Calcutta] Notification request XML => 719473849715035381391786REN325App [08-Dec-2022 20:21:23 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:23:34 Asia/Calcutta] Notification request XML => 719474569715452134901786REN325App [08-Dec-2022 20:23:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:39:40 Asia/Calcutta] Notification request XML => 719481929715696057441786REN325App [08-Dec-2022 20:39:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:41:53 Asia/Calcutta] Notification request XML => 719482901670512268158c317193c19715659852021786SUB00App [08-Dec-2022 20:41:53 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:44:11 Asia/Calcutta] Notification request XML => 719483849715065466951786REN325App [08-Dec-2022 20:44:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:46:50 Asia/Calcutta] Notification request XML => 719484951670512521499c317197c19715685188191786SUB00App [08-Dec-2022 20:46:50 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 20:47:30 Asia/Calcutta] Notification request XML => 719485299715472592711786REN325App [08-Dec-2022 20:47:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:03:32 Asia/Calcutta] Notification request XML => 719493519715016819161786REN325App [08-Dec-2022 21:03:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:13:48 Asia/Calcutta] Notification request XML => 719498821670514163349c317215c19715681692381786SUB00App [08-Dec-2022 21:13:48 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:19:45 Asia/Calcutta] Notification request XML => 688710929715674676211786UNSUB3250Ccare [08-Dec-2022 21:19:45 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:23:11 Asia/Calcutta] Notification request XML => 710905459715479844371786UNSUB00Ccare [08-Dec-2022 21:23:11 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:25:05 Asia/Calcutta] Notification request XML => 719506281670514837298c317217c19715429480571786SUB00App [08-Dec-2022 21:25:05 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:31:14 Asia/Calcutta] Notification request XML => 719508769715013596441786REN325App [08-Dec-2022 21:31:14 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:35:15 Asia/Calcutta] Notification request XML => 719510519715647143091786REN325App [08-Dec-2022 21:35:15 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:42:20 Asia/Calcutta] Notification request XML => 719513431670515913809c317250c19715444247611786SUB00App [08-Dec-2022 21:42:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:42:20 Asia/Calcutta] Notification request XML => 719513421670515877238c317244c19715669979681786SUB00App [08-Dec-2022 21:42:20 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:53:28 Asia/Calcutta] Notification request XML => 719517941670516554889c317272c19715439243181786SUB00App [08-Dec-2022 21:53:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 21:57:42 Asia/Calcutta] Notification request XML => 719520219715617357361786REN325App [08-Dec-2022 21:57:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:01:16 Asia/Calcutta] Notification request XML => 719521971670517029108c317281c19715689159661786SUB00App [08-Dec-2022 22:01:16 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:01:19 Asia/Calcutta] Notification request XML => 719522099715438092981786REN154App [08-Dec-2022 22:01:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:05:32 Asia/Calcutta] Notification request XML => 719524209715698960541786REN325App [08-Dec-2022 22:05:32 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:09:57 Asia/Calcutta] Notification request XML => 719526969715052239821786REN325App [08-Dec-2022 22:09:57 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:21:30 Asia/Calcutta] Notification request XML => 719535709715691353861786REN325App [08-Dec-2022 22:21:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:24:39 Asia/Calcutta] Notification request XML => 719538081670518441857c317323c19715678961661786SUB00App [08-Dec-2022 22:24:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:26:03 Asia/Calcutta] Notification request XML => 719539029715032170141786REN233App [08-Dec-2022 22:26:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:26:03 Asia/Calcutta] Notification request XML => 719539049715046924421786REN325App [08-Dec-2022 22:26:03 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:26:10 Asia/Calcutta] Notification request XML => 719539059715057416771786REN325App [08-Dec-2022 22:26:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:26:10 Asia/Calcutta] Notification request XML => 719539079715443380971786REN18App [08-Dec-2022 22:26:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:26:10 Asia/Calcutta] Notification request XML => 719539089715646671331786REN76App [08-Dec-2022 22:26:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:28:40 Asia/Calcutta] Notification request XML => 719540251670518662118c317333c19715446410221786SUB00App [08-Dec-2022 22:28:40 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:35:13 Asia/Calcutta] Notification request XML => 719542739715686022961786REN325App [08-Dec-2022 22:35:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:38:12 Asia/Calcutta] Notification request XML => 719543961670519249604c317356c19715661056271786SUB00App [08-Dec-2022 22:38:12 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:38:41 Asia/Calcutta] Notification request XML => 719544131670519255299c317357c19715448177591786SUB00App [08-Dec-2022 22:38:41 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:45:19 Asia/Calcutta] Notification request XML => 719547039715662646201786REN325App [08-Dec-2022 22:45:19 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:49:01 Asia/Calcutta] Notification request XML => 719549011670519850748c317381c19715026528041786SUB00App [08-Dec-2022 22:49:01 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:51:13 Asia/Calcutta] Notification request XML => 719550329715051623741786REN325App [08-Dec-2022 22:51:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 22:58:34 Asia/Calcutta] Notification request XML => 713470009715456506731786UNSUB00Ccare [08-Dec-2022 22:58:34 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:08:42 Asia/Calcutta] Notification request XML => 719561901670521071000c317417c19715626947851786SUB00App [08-Dec-2022 23:08:42 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:09:17 Asia/Calcutta] Notification request XML => 719562781670521115914c317420c19715646166421786SUB00App [08-Dec-2022 23:09:17 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:19:09 Asia/Calcutta] Notification request XML => 719570799715670870671786REN325App [08-Dec-2022 23:19:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:19:09 Asia/Calcutta] Notification request XML => 719570819715053011101786REN325App [08-Dec-2022 23:19:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:19:09 Asia/Calcutta] Notification request XML => 719570849715051225591786REN325App [08-Dec-2022 23:19:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:19:09 Asia/Calcutta] Notification request XML => 719570889715643124361786REN325App [08-Dec-2022 23:19:09 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:19:10 Asia/Calcutta] Notification request XML => 719570919715661872901786REN155App [08-Dec-2022 23:19:10 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:24:49 Asia/Calcutta] Notification request XML => 719573331670522053362c317441c19715097262161786SUB00App [08-Dec-2022 23:24:49 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:29:28 Asia/Calcutta] Notification request XML => 719575351670522321182c317450c19715616484631786SUB00App [08-Dec-2022 23:29:28 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:33:13 Asia/Calcutta] Notification request XML => 719576801670522542599c317455c19715627101421786SUB00App [08-Dec-2022 23:33:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:33:16 Asia/Calcutta] Notification request XML => 719576749715444642171786REN325App [08-Dec-2022 23:33:16 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:41:30 Asia/Calcutta] Notification request XML => 719579541670523052870c317464c19715478215531786SUB00App [08-Dec-2022 23:41:30 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:41:51 Asia/Calcutta] Notification request XML => 719579689715686602501786REN325App [08-Dec-2022 23:41:51 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:41:54 Asia/Calcutta] Notification request XML => 719579711670523069058c317465c19715617535971786SUB00App [08-Dec-2022 23:41:54 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:43:39 Asia/Calcutta] Notification request XML => 719580569715432564241786REN325App [08-Dec-2022 23:43:39 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:51:36 Asia/Calcutta] Notification request XML => 719584101670523671378c317487c19715051278351786SUB00App [08-Dec-2022 23:51:36 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42

[08-Dec-2022 23:58:13 Asia/Calcutta] Notification request XML => 719586811670524048760c317500c19715479575861786SUB00App [08-Dec-2022 23:58:13 Asia/Calcutta] Curl output response => HTTP Status 415 – Unsupported Media Type

HTTP Status 415 – Unsupported Media Type


Type Status Report

Description The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.


Apache Tomcat/8.5.42