I am trying to download a file from a local web server. While IE works fine, Firefox appends an underscore at the end of the filename and Chrome appends hyphensemi-colon at the end.
Any pointers to look at?
Thanks,
Related
We uploaded an updated version of an Excel file to our client portal. Tested it on our test account and it downloads the most up-to-date file.
The client that needs to retrieve it is using Chrome and when they download it they say they keep getting the old file without the updates. They switched to IE and it downloaded the file fine.
Sounds like a caching issue with Chrome, but I did have the press CTRL + F5 and they said it didn't clear up the issue.
Anyone experienced this issue before? If it isn't user error, what is the solution?
You can usually force the browser to get a new version of a file by putting a query string after it, something like ?v=2.0 should be enough.
I have to open a file via a HTML-link.
The file's location is on another computer and adressed by the IP adress (passing through a custom server tool)
EG:
<a href="http://localhost:PORT/FILE.dotx" download>Download</a>
This works in firefox and chrome just fine, but IE (Version 8) interprets the file as a xml-File and tries to open it directly.
There is no possibility to upgrade or change the client's browser.
Is it possible to force IE to download the file without using PHP, VB or Rails?
(as we don't have a apache server or something like this)
lighttpd.conf sample, requires mod_setenv:
$HTTP["url"] =~ "\.pdf\?dl$" {
setenv.add-response-header = ( "Content-Disposition" => "attachment")
}
This is the only reliable way. IE won't trust MIME types because of an old Apache flaw workaround where Apache sent wrong MIME types and Microsoft "fixed it".
While all pdf files could simply be given the downloading header, I have chosen to show a neater way - only the parameter ?dl activates this behavior. Plain pdfs will still display in-browser and only a link which has ?dl appended gets the special treatment.
I am actually using this technique on my server, but it is implemented in php because I can't make do with the static handlers alone. Since I offer images through this, I also add the Cache: no-transform header to prevent Opera Turbo from recompressing the file to be downloaded.
EDIT: Fixed the Disposition word - has to be capitalized to also work in Webkit-based browsers.
I accidentally deleted a HTML file with dreamweaver. I really would like to get this file back, my backup was not ok. So I would like to retrieve the file using the cache of my browser Chrome. I Googled and found this: LINK But it doesnt work for me, when I download the file and look at it in Notepad all I see is strange characters.
What else can I try to get my file back with Chrome cache?
NirSoft's ChromeCacheView worked perfectly for me.
http://www.nirsoft.net/utils/chrome_cache_view.html
Note that the option to restore the actual files is not that obvious. F4 does it.
It would not be easily extractable from it's hexadecimal representation.
I have recently created a script for extracting files from Chrome and Firefox cache. Check it out at this gist.
See the usage guide in this post.
What you download on this site is a gzip file, if you open that in notepad you will get much the same as on the chrome://cache site. You need to extract it with 7zip or a similar tool first.
I have a XSLT sample copied straight from http://www.w3schools.com/xsl/xsl_transformation.asp, which I can't seem to view in Google Chrome. However, it seems to work fine in IE.
Does anyone know why this would be?
EDIT:
The online version works fine, but the local copy does not.
I had same issue with Google Chrome (tested on 13.0.782.215) and (non-JavaScript XSL transformation):
<?xml-stylesheet type="text/xsl" href="simple.xsl"?>
Online transformation works well e.g. http://www.w3schools.com/xml/simplexsl.xml
Local transformation (without server like Apache) show just blank page
I found solution that works for me is to run Chrome browser with --allow-file-access-from-files switch:
// By default, file:// URIs cannot read other file:// URIs. This is an
// override for developers who need the old behavior for testing.
const char kAllowFileAccessFromFiles[] = "allow-file-access-from-files";
Yeah, if you copied the sample down to a file on your computer, the xml won't work with xslt on chromium because it can't find your xslt file provided by just its filename. I've tried put both the xml file and the xslt file to a web server running on my computer and it worked.
If you don't have a web server on your computer, I have no solution with chromium. But maybe you can try a full path, maybe begun with "file:///C:/". Use other browser if that doesn't work...
Good luck,
Max Xie
I recently built a HTML and Javascript web application that opens specific folders throughout a network of accessible drives. This app works well when it is rendered in IE; however, the folder paths do not work in FireFox.
The following is an example of the path format that I am using to open the folders in IE:
{
window.open('\\\\Server-1\\Folder-1\\Folder-2');
}
The path actually has 4 backward slashes at the beginning and 2 bakcward slashes between each folder. It appears different when rendered.
When I run this app in FireFox, the window or new tab appears, but there is nothing rendered. I've manually entered the path and FireFox converts it to: file://///Server-1/Folder-1/Folder-2. Does anyone know what the correct syntax would be (i.e. window.open(?...))?
Here is something that might help you. It is considered a security risk by Mozilla.
http://kb.mozillazine.org/Links_to_local_pages_do_not_work
according to Daniel's link you need THREE forward slashes not FOUR for local paths...
Path Syntax
You also need to use proper URI syntax
for local file references. It is not
proper to enter an
operating-system-specific path, such
as c:\subdir\file.ext without
converting it to a URI, which in this
case would be
file:///c:/subdir/file.ext. In
general, a file path is converted to a
URI by adding the scheme identifier
file:, then three forward slashes
(representing an empty authority or
host segment), then the path with all
backslashes converted to forward
slashes.