On Tue, May 31, 2016 at 7:06 PM, Francis Daly wrote:
> On Tue, May 31, 2016 at 04:48:19PM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
>> > On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
>
> Hi there,
On Tue, May 31, 2016 at 04:48:19PM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
> > On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
Hi there,
> > It sounds like your design is that your client sends a http request to
> >
On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
> On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
>> > On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
>
> Hi there,
On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
> > On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
Hi there,
> >> The C++ app sends the request directly to port 8000. With the django
> >>
On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
> On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
>
> Hi there,
>
>> > Possibly one of them covers what you want?
>>
>> There are 2
On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
Hi there,
> > Possibly one of them covers what you want?
>
> There are 2 ways requests get to port 8000, which is the port I want
> to check headers on.
>
On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
> On Tue, May 31, 2016 at 09:23:36AM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 7:55 AM, Larry Martell
>> wrote:
>> >>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
On Tue, May 31, 2016 at 09:23:36AM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 7:55 AM, Larry Martell
> wrote:
> >>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
> >>> wrote:
Hi there,
> Is there any way with nginx to check a
On Tue, May 31, 2016 at 7:55 AM, Larry Martell wrote:
> On Tue, May 31, 2016 at 7:41 AM, Larry Martell
> wrote:
>> On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
>> wrote:
>>>
>>>
>>> On Sat, May 28, 2016
On Tue, May 31, 2016 at 7:41 AM, Larry Martell wrote:
> On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
> wrote:
>>
>>
>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>> wrote:
>>>
>>> Is there any way
On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
wrote:
>
>
> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
> wrote:
>>
>> Is there any way with nginx to check a request's headers and send back
>> a 401 if the headers are not
On Sat, May 28, 2016 at 12:48 PM, Larry Martell
wrote:
> Is there any way with nginx to check a request's headers and send back
> a 401 if the headers are not proper?
>
Yes, you can do with this via the 'map' and 'if' directives. A trivial
example:
http {
# if
Is there any way with nginx to check a request's headers and send back
a 401 if the headers are not proper?
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
13 matches
Mail list logo