The API should work fine even with 1.1 request . FetchURL/Pages uses the HTTPConnectAPI which eventually uses the HTTP state machine, which eventually uses the right version to talk to Origin Sever.

So the diagram looks some thing like this.
plugin-API-State Machine-Origin Server

as you can see above the version between plugin and API does not really matter and API always uses 1.0 request and creates a new state machine.

Also , you can see that persistent connections to client or Origin Server is not based on the request from plugin to API.

I have the following questions :
Have you tested the API with 1.1 requests?
How are you using the API ?

Thanks,
Vijay

Yes, I understand the request works for 1.0 requests and underneath it transforms to 1.1 request in the state machine. I am changing my request explicitly to 1.0 before I call TSFetchURL. However, one would expect it to work with 1.1 request passed to the TSFetchURL as well, regardless what happens within state machine. Passing a 1.1 request freezes the server till time out.

I agree that it should work with 1.1 requests , if it is timing out there might be a bug in the API when it is changing the request to 1.0

-Vijay

Hi Naveen,

Are you seeing the timeouts for 1.1 requests? If Not, i would like to close this bug

-Vijay

Moving out to 3.1.1, until we get a confirmation if this can be closed, or needs more work.

I've not checked it. With version 3.0, TSFetchURL signature has changed in the header, but the binary has a different signature. It doesn't even compile for me.

many APIs changed prototypes, but should be an easy fix. There's even a little perl script (tools/apichecker.pl) to help the migration of plugins to 3.0.

The prototype change is fine, but they have a different signature from their implementation.

InkAPI.cc:
TSFetchUrl(const char* headers, int request_len, unsigned int ip, int port , TSCont contp, TSFetchWakeUpOptions callback_options,TSFetchEvent events)
ts.h.in:
tsapi void TSFetchUrl(const char* request,int request_len, struct sockaddr const* addr, TSCont contp, TSFetchWakeUpOptions callback_options,TSFetchEvent event);

That seems a bug that must have happened during IPv6 changes. Alan?

I'm moving all 3.1.2 bugs out to 3.1.3, and we can move some 3.1.1 bugs out to 3.1.2, to get some release action going.

Moving out to v3.3.0, move back to 3.1.4 if this will be work on soon.

Moving to 3.3.2.

Moving to 4.2.0 as per https://cwiki.apache.org/confluence/display/TS/New+Release+Processes