New answers tagged

0

First you need to find out the exact reason why it starts giving out a 503 error. It could be resource exhaustion or configuration issue. If it is a configuration problem, then you change configuration to allow more simultaneous requests. If it is resource exhaustion, then you can do the following things: You can optimize your web application so that it ...


1

Let's consider that you are trying to boot BIOS clients if your NBP is pxelinux.0 then you won't be able to use the HTTP capabilities. For HTTP and FTP transfers you must use lpxelinux.0 instead. The prepending "l" stands for the use of the lwIP (lightweight IP) library.


0

This solution uses conditional logic, but as the accepted answer suggests, I also think this is ok. Ref: http://stackoverflow.com/questions/4833238/nginx-conf-redirect-multiple-conditions Also, this doesn't require opening any additional ports in the aws security settings for the image. You can terminate ssl in the AWS LB, and route https traffic to http ...


1

This NOT allowed. According to the HTTP specification (RFC 2616), Content-Encoding is NOT one of the possible request header fields, therefore it is not possible to compress the request entity body as there is no legal way to let the server know this has occurred. Any compression of the request body is done only as a non-standard extension.


0

It is required by the RFCs, a point previously made here: http://stackoverflow.com/questions/3364144/is-port-number-required-in-http-host-header-parameter The question was why, and the RFC's requirement does seem a bit contrary to normal layering. After all, the port is a property of the transport connection and not of the application (or session) layers. ...


0

Most of the internet website traffic is done on standard port 80. For this case, a port number can (according to RFC should) be omitted. HTTPS traffic is usually done on port 443 in which case a browser will include it by default. Connection to any other port is a fairly special case (mostly for development or separation of services). So yes, if you want to ...


0

Look at who made the HTTP2 standard http://ietf.org/. Speak with the guys there. They have chat, discussion groups, etc. Even though I disagree with your opinion, thank you for taking time to improve standards!


1

The fast answer no "No". Keep-Alive headers are HTTP 1.0 syntax and are not included i the HTTP 1.1 definition. HTTP 1.1 defaults to persistent connections, and does not need a mechanism to request them. Please refer to the RFCs for questions like this. HTTP 1.1 us defined in RFCs 7230 thru 7237. The RFCs are available in a number of formats. From the ...


1

Yes, this is correct. The server can just say "I don't support your keep-alive request and will just close the connection when I am finished". From RFC 2616, Section 14.10: HTTP/1.1 defines the "close" connection option for the sender to signal that the connection will be closed after completion of the response. For example, Connection: close ...


1

You can use the addition module (ngx_http_addition_module), which needs to be enabled at build time (--with-http_addition_module): location / { add_before_body /before_action; add_after_body /after_action; } Note that it does not permit stacking of arbitrary data, but instead provides features to add content before and after the main response. It ...


0

The sendfile off solution is not working for me. I've fixed it by disabling the open_file_cache.


0

Most of the time when people have problems with MIME types, is because IIS is not configured to serve a file with a certain MIME type, the http status code for that is 404.3, Your 406 means the client has sends an http accept header which is not understood by the server. A typical accept header would be: Accept: text/html,application/xhtml+xml,application/...


0

Add .img to the MIME types list as application/octet-stream


2

No RFC seem wrote for that ! but there is some default value from major web server. IIS: connectionTimeout; The HTTP.sys Timer_EntityBody timer expired. The connection expired before the request entity body arrived. When it is clear that a request has an entity body, the HTTP API turns on the Timer_EntityBody timer. Initially, the limit of this timer is ...


0

you can achieve that using the unix socket commands. Take a look at point 9.2 of the management.txt doc file. There are third party tools that use this 'api' like haproxyctl, but I do not have any experience with them.


0

Apache will always respond to properly formatted requests. However, if you setup a default SSL virtual host you can return 404 or other error response to all requests. If the requested domain does not match the supported domains, the response should also trigger and SSL domain mismatch error.


0

from the IIS log. it shows that the web service could not be reached or it not available " /webservice/webservice.asmx 400 ". Run the web service separate to confirm if the web service is up and running in the same server where the windows service is hosted. Also this could be a network issue if the windows service and the web service are in different ...



Top 50 recent answers are included