Show all posts by user
What you'd like to see in nginx
Re: echo_location Not Working - 10 years ago
I'm an idiot, it's because I didn't have the SSI module compiled in.by adamchal - Nginx Mailing List - English
echo_location Not Working - 10 years ago
Anybody having issues with the echo_location (and echo_location_async) directive? I have tried to get this to work with v1.1.18 and v1.3.6, and they both exhibit the same behavior. Basically, only the output from the /main block is echo'd out. My nginx config (basically a copy-and-paste) from the echo module's documentation: location /main { echo_reset_timer; echo_locby adamchal - Nginx Mailing List - English
Re: Adding $request_path Variable - 10 years ago
kolbyjack, this is really smart. I didn't think about this approach. The only downside is doing an additional regex for each request. But, in the meantime, this will work. Thanks!by adamchal - Nginx Mailing List - English
Re: Adding $request_path Variable - 10 years ago
I've tried a bunch of approaches in the nginx.conf to get the original request path isolated to a variable for logging, but all have failed. I'm pretty desperate for this variable, but I don't have the time to apply a patch to the source code. I'm willing to pay for someone to do this. If anyone is interested, just let me know. It really shouldn't be that complicated.by adamchal - Nginx Mailing List - English
Re: Adding $request_path Variable - 10 years ago
António, this was a really good idea, but with fastcgi_intercept_errors and proxy_intercept_errors turned on, the $orig_uri is logged as whatever the error_page is (in my case /error.html).by adamchal - Nginx Mailing List - English
Adding $request_path Variable - 10 years ago
It would be very nice if someone would add the following variable to Nginx: $request_path Right now, we have $request_uri which includes the query string of the original request. We also have the $uri which is the path portion of the $request_uri, but it is the path AFTER the rewrites. What would be very useful is the $request_path, which would be the original path portion of the $request_by adamchal - Nginx Mailing List - English
Re: Collapsing Empty Variables in Nginx Access Log When Using TAB Delimiter - 11 years ago
What I've done for now is replace the lines at 675 and 676 of (src/http/modules/ngx_http_log_module.c): 674: if (value == NULL || value->not_found) { 675: *buf = '-'; 676: return buf + 1; 677: } with: 674: if (value == NULL || value->not_found) { 675: *buf = 0; 676: return buf; 677: } I hope this won't cause any issues. It seems toby adamchal - Nginx Mailing List - English
Re: Collapsing Empty Variables in Nginx Access Log When Using TAB Delimiter - 11 years ago
Yeah, it would be awesome if I could replace the '-' with just an empty string. Does anyone have a good idea of how to implement? The line that currently sets the '-' as the NULL character in the logs is: src/http/modules/ngx_http_log_module.c:675 I thought about just writing a patch for it, but I'm not sure if that would mess things up in the future. Even still, what's the best way of doby adamchal - Nginx Mailing List - English
Re: Collapsing Empty Variables in Nginx Access Log When Using TAB Delimiter - 11 years ago
OK, I just knocked-out 50 push-ups as a punishment for this. There's absolutely nothing wrong with the logging module. Apparently, the Mac OS X Term was messing this up while I was copying and pasting into Textmate. I ran the logs through `cut` as well as a custom line parser and it's working perfectly fine. I apologize for the confusion, but trust me that I actually blew a day and a half wresby adamchal - Nginx Mailing List - English
Collapsing Empty Variables in Nginx Access Log When Using TAB Delimiter - 11 years ago
I'm noticing that Nginx's log module is "collapsing" empty log variables primarily when using a TAB (\t) as a delimiter in the access log. For example, if I use the following: log_format main '$server_name $msec $remote_addr $cookie_x $cookie_y $cookie_z $status'; And a request does not have any cookies set (so $cookie_x, $cookie_y, and $cookie_z would be empty), then I wouldby adamchal - Nginx Mailing List - English
Caching 0-byte 200 Status Responses - 11 years ago
I have a problem with Nginx's cache when an upstream returns a 0-byte 200 response. These 0-byte responses are very rare, but they are really apparent when the 0-byte 200 response gets cached for 1 hour. With Nginx, you're able to set different TTLs for specific response codes, but I cannot figure out a way to set a really low TTL for a 0-byte 200 response or treat it like a 500 status code.by adamchal - How to...
auth_request + Multiple set $memcached_key - 11 years ago
Currently, I'm using auth_request for with memcache to provide super-fast non-blocking authentication. I love it. I noticed, however, I cannot do another memcache query with a different key if the location is being auth_request'd first. Given the following config for example: # everything by default must be authenticated auth_request /_auth; # authenticationby adamchal - How to...
Re: [ANNOUNCE] auth request module 0.2 - 11 years ago
I actually got this working with the built-in memcache and userid modules. This is REALLY cool and I'm going to be re-thinking how to provide security/authentication in other projects using this approach. Thanks for the quick feedback and your hard work Maxim. Here's a snippet of my configuration: server { ... auth_request /auth; location = /auth { auth_rby adamchal - Nginx Mailing List - English
Re: [ANNOUNCE] auth request module 0.2 - 11 years ago
OK, you're absolutely right. I didn't have that line in there. I'm trying to follow the reasoning for needing to zero-out request body, but it doesn't make immediate sense. Is the OP in this thread along the same lines? http://forum.nginx.org/read.php?2,206860by adamchal - Nginx Mailing List - English
Re: [ANNOUNCE] auth request module 0.2 - 11 years ago
I'm having problems using this module for POST requests. GET works fine and it's really awesome, but POST requests end-up timing out. Anybody experience the same thing?by adamchal - Nginx Mailing List - English
Re: Scribe log output. - 12 years ago
That looks a little rough, but it might be as simple as that. Have you tried that out?by adamchal - Ideas and Feature Requests
Re: Scribe log output. - 12 years ago
Agreed. Anybody have any luck doing this with Nginx? Kinda sucks collecting logs…Scribe module would be sweet.by adamchal - Ideas and Feature Requests
Re: cache gzipped content with proxy_pass - 12 years ago
I've been following this discussion and I'm anxiously waiting for some resolution. I think Maxim's approach is right: implementing a gzip_cache filter that could be used for caching any content. This would allow for much more flexibility than just using it for proxy_pass/proxy_cache. This could effectively eliminate the gzip_static filter. If you have plain HTML served and "gzip on;&quoby adamchal - Nginx Mailing List - English
Re: Scribe log output. - 12 years ago
This would be awesome.by adamchal - Ideas and Feature Requests
Re: GEOIP context problem - 12 years ago
This really sucks. It'd be MUCH better if you could simply inherit the fastcgi_param. I've now come across this a bunch of times with different projects. It'd be nice for example to pass DEBUG 1 or DEBUG 0 to the fastcgi handler. The documentation makes sense after you read it a bunch of times, but at first read, it makes it seem like you can inherit portions of fastcgi_param.by adamchal - Nginx Mailing List - English
 |
 |
 |
 |
|