Unfortunately I still cannot find out how to send data to upstream and force 
nginx to not wait for reply. Is really upstream suitable for my purpose?

Regards,
Daniel

______________________________________________________________
> Od: [email protected]
> Komu: <[email protected]>
> Datum: 16.06.2013 18:33
> Předmět: Re: Proxy module without waiting for a reply
>
>Hello.
>But when I send data through upstream then Nginx waits until it can read some 
>data from the upstream server, finally it times out. But I would need to 
>finish the upstream request just after data are written without any waiting 
>for the reply from upstream server. Is there any way how to force it to work 
>this way?
>
>Thanks,
>Daniel
>
>______________________________________________________________
>> Od: "Maxim Dounin" <[email protected]>
>> Komu: <[email protected]>
>> Datum: 09.06.2013 14:04
>> Předmět: Re: Proxy module without waiting for a reply
>>
>>Hello!
>>
>>On Sun, Jun 09, 2013 at 11:21:39AM +0200, [email protected] wrote:
>>
>>> Hi all,
>>> I need to implement nginx module that does the following:
>>> * It receives http get requests.
>>> * For every request it sends information about the request over TCP packet
>>> to another server.
>>> * When data are send it generates some trivial HTTP reply. The another
>>> server does not sent any reply to the module.
>>> 
>>> I studied source code of other modules and some tutorials and it seems that
>>> I should implement upstream (proxy) module. But I would like to achieve the
>>> following:
>>> * Module does generate the reply just after data are sent to another
>>> server. It does not wait for any reply from another server.
>>> * Socket to another server remains open among requests and is reused for
>>> subsequent requests.
>>> 
>>> Is this possible and is implementation of upstream module the right way?
>>
>>Yes, it looks possible and easy enough.
>>
>>-- 
>>Maxim Dounin
>>http://nginx.org/en/donation.html
>>
>>_______________________________________________
>>nginx-devel mailing list
>>[email protected]
>>http://mailman.nginx.org/mailman/listinfo/nginx-devel
>>
>
>_______________________________________________
>nginx-devel mailing list
>[email protected]
>http://mailman.nginx.org/mailman/listinfo/nginx-devel
>

_______________________________________________
nginx-devel mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx-devel

Reply via email to