The best solution would be to read in the file, then decide which kind of image it is and send out the appropriate header $filename = basename($file); $file_extension = strtolower(substr(strrchr($filename,”.”),1)); switch( $file_extension ) { case “gif”: $ctype=”image/gif”; break; case “png”: $ctype=”image/png”; break; case “jpeg”: case “jpg”: $ctype=”image/jpeg”; break; case “svg”: $ctype=”image/svg+xml”; break; default: } header(‘Content-type: … Read more
Just quoting the OP as he found the solution, but forgot to add it as an answer: Edit: I found the solution thanks to a co-worker: struct pjsip_generic_string_hdr CustomHeader; pj_str_t name = pj_str(“MyHeader”); pj_str_t value = pj_str(“HeaderValue”); pjsip_generic_string_hdr_init2(&CustomHeader, &name, &value); pj_list_push_back(&cfg.reg_hdr_list, &CustomHeader); This seems to work as expected.
If the header already exists: client.Headers.Set(“Content-Type”, “image/jpeg”); if its a new header: client.Headers.Add(“Content-Type”, “image/jpeg”); Also, there is a chance that you are getting an error because you are trying to set the headers too late. Post your exception so we can let you know. Update Looks like there are some weird restrictions on the “Content-Type” … Read more
Nope, it’s a vestigial header nowadays; that is to say, it was put there to work around a bug in a browser which is obsolete (several generations older than IE6 – the bug was reported fixed as of 1997, 15 years ago!) and nobody uses it any more. The patch to remove it is in … Read more
This feature was added to Capybara on April 25th, 2011 with this commit – https://github.com/jnicklas/capybara/commit/a00435d63085ac2e74a0f64e7b7dedc0f7252ea9 You can can now specify a custom header when using a custom Capybara driver. See http://automagical.posterous.com/creating-a-custom-capybara-driver for code examples.
Per the spec, it is used in age calculations. If you don’t know what time the server thinks it is, you won’t be able to calculate the “age” of a resource. Here’s the relevant text from the spec: Summary of age calculation algorithm, when a cache receives a response: age_value is the value of Age: … Read more
Quick pure JavaScript implementation: function MessageBar() { // CSS styling: var css = function(el,s) { for (var i in s) { el.style[i] = s[i]; } return el; }, // Create the element: bar = css(document.createElement(‘div’), { top: 0, left: 0, position: ‘fixed’, background: ‘orange’, width: ‘100%’, padding: ’10px’, textAlign: ‘center’ }); // Inject it: document.body.appendChild(bar); … Read more
This is not possible. A JSONP request works by creating a <script> element with its src attribute set to the request URL. You cannot add custom headers to the HTTP request sent by a <script> element.
Not including the accept-encoding header implies that you may want the default encoding, i.e. identity. The caveat here is that the RFC2616 sec 14.3 allows the server to assume any available encoding is acceptable. To explicitly request plain text, set ‘accept-encoding: identity’
As you mentioned, you’d have to know the encoding of the file to read the encoding attribute. However, there is a heuristic that can easily get you close enough to the “real” encoding to allow you to read the encoding attribute. This works, because the <?xml part by definition can only contain characters in the … Read more