http-headers

I am using Django to develop a new website and I am facing a problem with an ajax request. I have been googling a lot and read a lot of posts and articles (most of them explain the same). The issue: The ajax call is executed and I received the request in the view, but the request.is_ajax() returns false. For what I know the request.is_ajax() checks the value of the HTTP_X_REQUESTED_WITH header, but I can't see it in the request headers, thus I cannot check the is_ajax() in my view. HTML form: <form id="search-form" method="get" action="/search/"> <input type="text" id="search" name="search"

Why preemptive authentication required ? System.setProperty("httpclient.authentication.preemptive", "true"); I had written web services access client program in java. Where we were setting username and password in call object and that was working perfectly. Recently, our service provider made some changes at their side and after that they were not receiving username & password in web service call and as they were not receiving username & passwod so we were not able to connect to their (provider) service. Then i did googling and found about preemptive authentication. While calling web services

I have a website where virtual hosts are defined in /etc/apache2/sites-enabled/ with a header being set with the always option like this: Header always set X-Frame-Options DENY If I now set the same header using .htaccess in the web site's root folder, but without always then the header is returned twice in the server's response. The setting in .htaccess (amongst others): Header set X-Frame-Options DENY The server's response: HTTP/1.1 200 OK Date: Mon, 02 May 2016 16:02:29 GMT Server: Apache/2.4.10 (Debian) X-Frame-Options: DENY Cache-Control: no-cache, no-store, must-revalidate, private

In my instance, I have Glassfish 3.1.1 / Mojarra 2.1.3 I could remove the X-Powered-By in Glassfish Admin Console in the Network listener (so it doesn't show the long text: Servlet/3.0 JSP/2.2 (GlassFish Server Open Source Edition 3.1.1 Java/Sun Microsystems Inc./1.6) but it still shows (yes, twice): X-Powered-By: JSF/2.0 X-Powered-By: JSF/2.0 I am using Jersey and JAXB to expose some web-services and have some servlets deployed using the @WebServlet Annotation but I don't think they add anything. It is not generated by mod_jk or Apache because I get those headers even when connecting to the

I've encountered the same problem as described in this post: Google Calendar api v3 re-update issue Namely, once I create an event and update it once using the Google Calendar API (v3), I am no longer able to update the event. When I attempt to, I get a 400 - Invalid value response. (FWIW I'm working in PHP). Following a lead offered in the post I referenced above, I attempted to solve the issue using etags (though admittedly my grasp of how they work is limited). Basically, on event update, the API returns an etag in its response, which I now save in my database. Then for subsequent (n > 1)

OK. I'm sure it does download XML files with the .xml extension, but I'm wondering what is missing in the code here to cause the .xml extenstion to be missing from the downloaded file. Note: This works in IE 6+ (didn't try WebKit based browsers or Opera) private void GenerateXmlAttachment(string xmlInStringFormat, string fileName) { // Where fileName = "someFile.xml" HttpResponse response = HttpContext.Current.Response; response.Clear(); response.Charset = string.Empty; response.ContentEncoding = Encoding.Default; response.AddHeader("Content-Disposition", "attachment;filename=" + fileName);

I recently discovered something (that surprises me) when opening an audio file in firefox or chrome. If I don't specify the HTTP response header "Accept-Ranges: bytes", firefox won't be able to determine the length of the ogg file (in seconds) before reaching the end in playback. Chrome will discover the length of the ogg file (in seconds), but the audio player appears to crash when it reaches the end, and refuses to re-play the file after the crash. Other browsers were not tested. Working Http response headers: HTTP/1.1 200 OK Accept-Ranges: bytes Content-Type: application/ogg Content-Length: