AnsweredAssumed Answered

Expect 100-continue Header issue in virtual service

Question asked by Nandeesha on Jul 20, 2015
Latest reply on Jul 27, 2015 by ravikumar.ser
When .net client applications make a call to a virtual service with Expect 100-Continue Header. We actually see two calls being made.
The first call is a HTTP 100-Continue call that does not have the request body. This call expects a 100-Continue response
The second call contains the actual payload.

 

For the first call virtual service sending back to client Match Not found response with mentioned below Headers
HTTP/1.1 100 Continue
Server: LISA/Virtual-Environment-Server
Date: Mon, 20 Jul 2015 15:53:52 IST
X-Powered-By: LISA/8.0.1 (8.0.1.644); Interactive TKO, Inc.
Content-Type: null
Content-Length: 0
The second call contains the actual payload and the virtual service sending back with a proper response to client
Note : I twick the model to handle empty request not to send live invocation

 

The issue here when we switch the mode to "learning or live or Failover" the virtual service will die by omitting response as mentioned below for the second call which contains the actual payload request

HTTP/1.1 400 Bad Request
Server: Microsoft-HTTPAPI/2.0
Date: Mon, 20 Jul 2015 10:24:06 GMT
Content-Length: 326
X-Powered-By: LISA/8.0.1 (8.0.1.644); Interactive TKO, Inc.
Content-Type: text/html; charset=us-ascii

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Verb</h2>
<hr><p>HTTP Error 400. The request verb is invalid.</p>
</BODY></HTML>

 

I have captured the same and the attached the screen shot for the reference .

 

I appreciate your help regarding the same

 

promotion.png

 

Thanks

Nandeesha

Outcomes