"Nginx HTTP Server" book published

By -
Nginx HTTP Server was published and is now available for purchase on various locations. It will begin to appear in store in the coming weeks. You can already purchase the eBook from the publisher's website at the link below:
https://www.packtpub.com/nginx-http-server-for-web-applications/book
The eBook can be purchased for 23.79€ whereas the book is 31.49€.
There is also a preview chapter available on the website for anyone to read!
Please feel free to leave your comments, feedback and questions if you have read the book.

Comments

Ryan Snowden/boxedthrills said…
Great work Clement. I hope to review your book soon. a big fan of Nginx ;)

Regards
Ryan from Beijing
Wed Aug 04, 11:48:00 PM
Clément Nedelcu said…
Hehe, thanks Ryan... another Nginx user from China!
Thu Aug 05, 12:01:00 AM
Anonymous said…
Hello Clément,

I have been asked by Packt Publishing to write a review of your Nginx book, and I thought it would be a nice idea to do it in the form of little email Q&A with you.
You can contact me at ludovf.net.

Let me know what you think,

Ludovico Fischer
Fri Aug 13, 08:50:00 PM
Clément Nedelcu said…
Hello,

OK, we could do that.
I will send you an email if I can find your address.
Fri Aug 13, 08:54:00 PM
Unknown said…
Hi,

you are french, it would be nice to have a french version ;)

Greg
Wed Sep 22, 08:48:00 PM
Clément Nedelcu said…
I mentioned it to my publisher but I think it'll depend on the sales. Besides I don't know if they do books in other languages too...
Wed Sep 22, 09:37:00 PM
tt said…
Hi!
Please help me! I want to translate the book "Nginx HTTP Server" into chinese,because this book is very good! But I don't what I do , in other words, I need to know to contact !
Give me help ,thanks

my e-mail:ltgzs777@126.com
Fri Nov 05, 05:05:00 PM
Anonymous said…
i think this's very useful book for me,but i can't buy in China. few days ago,i read another book about Nginx writen by Zhang yichun. now i wanna get more information from your book. i hope to have chance to study with you.

Frank from Jiangsu Wuxi
email: wangxyong2001@163.com
Mon Nov 22, 11:11:00 AM
Anonymous said…
e... I think I make a mistake , that book writen by Zhangyan which i have read.
I've watched the video about Nginx by Zhangyichun. but it's difficult for me ... hehe =.=！

frank from Jiangsu Wuxi
email: wangxyong2001@163.com
Tue Nov 23, 08:46:00 PM
Karl said…
:P Now just got to release another book to cover the stable 1.0.0 branch :D
Tue Nov 08, 03:49:00 AM
Clément Nedelcu said…
I've given it some thought but there isn't anything major that justifies an update of the book. As far as I can tell everything that's in the book works as of v1.0.0 and I don't see any major feature that could require an update of the book. Sure the directive index could be updated and all but then how often are you going to do it? new stable versions are frequent and little things get added often :)
Tue Nov 08, 07:14:00 AM
Post a Comment

Popular posts from this blog

Nginx error 413: Request entity too large Quick Fix

By -
A quick article today about a common error people encounter with Nginx: the infamous 413 Request Entity Too Large HTTP error. I had the problem myself just yesterday on one of my newly configured servers, so I thought I'd make a blog post about it to make sure I don't forget this next time. Error 413: what does it mean? This error shows up when a visitor sends too much data in the HTTP request. This is normally caused by: • an overy large file being uploaded by the visitor • more generally too much POST data being sent by the client The fix is as simple as setting a directive in your Nginx configuration, read on below. How to fix it? client_max_body_size To fix this, you need to increase the value of the client_max_body_size directive. This directive defines the maximum amount of data Nginx will accept in an HTTP request. By default this value is set to 1 megabyte, meaning if you attempt to upload a file larger than 1 megabyte you'll be getting an  Error ...
Read more

Dealing with Nginx 400 Bad Request HTTP errors

By -
Today I'll write about something I experienced personally, on my websites. Some visitors reported that they were getting a "400 Bad Request" Nginx error randomly when visiting pages. And when they start getting that error, they can't access the site anymore: it'll output the same error no matter the page, until you "clear your cache and cookies". The error is easily understandable and is likely to be caused by... too much cookie data. Every time a visitor loads *any* page/content/file of your website, it sends the cookie data to the server. Cookie data is sent under the form of 1 header line starting with "Cookie: ". Basically, Nginx by default is configured to accept header lines of a maximum size of 4 kilobytes. When a line in the headers exceeds 4 kilobytes, Nginx returns the '400 Bad Request' error. Cookie data sometimes gets big, so it causes the error. It particularly happens on forums like vBulletin, Invision and others...
Read more

Affiliate module for Interspire Shopping Cart

By -
Image
Hello, I have already implemented this module on two shops rather successfully. The concept is quite simple: websites that want to get rewarded through affiliation must link to your website using an identifier in the URL. If your website is http://website.com/, then your links must be of the form http://website.com/?ref=123 where 123 is the affiliate ID. when a visitor clicks the link, the affiliate ID will be placed in a cookie that will expire after 15 days (this can be configured) when the visitor purchases an item: if the affiliate ID cookie is still enabled, the affiliate will be credited of a certain amount, it can be a share of the sale or a fixed amount. affiliate accounts are simple customer accounts, there is no modification to make regarding accounts. When a sale is made, they receive store credit. They can either spend the store credit to purchase items on the store, or they can manually request for a withdrawal (managing withdrawals is up to you). I will detail the i...
Read more