I try to download a file from ASP.NET Core to Electron app.
I see that ASP.NET Core properly quotes filename in content-disposition header but Electron cuts it to the first comma.
If I add extra double quotes in ASP.NET Core it works correctly (but adds additional undescores for normal browsers). Is it an issue with Electron or am i missing something?
To be more specific:
From ASP.NET Core Content-Disposition header send is
attachment; filename="[User, Test]"; filename*=UTF-8''%5BUser%2C%20Test%5D
In Electron filename received is
[User
Now if i artificially add quotes:
attachment; filename=""[User, Test]""; filename*=UTF-8''%5BUser%2C%20Test%5D
It will be ok in Electron
Related
I'm working on an hub ms.vss-web.hub extension for azure devops and I'm facing emoji rendering issue (text is within a diff monaco text editor)
looking at the html source, the emoji is not rendered as well
during development, I was using baseUri (https://learn.microsoft.com/en-us/azure/devops/extend/develop/manifest?view=azure-devops#runtime-attributes) and it was working as expected.
(below, display & source in devops, but with extension served from my laptop)
emoji rendering is failing in all parts of the page, not only monaco editor (I would exclude monaco editor from suspects)
html page is correctly in UTF8
I've checked html page after tfx extension create process (unzip) and encoding & emoji were still ok
I suspect an intermediate process done by devops while rendering.
I forced UTF8 with BOM rather only UTF8 and it fixed the issue.
Why are .html file parsed rather than compiled when open them in browser such as Safari? From the internet, I learned that parser is a component of a compiler. People say .html is parsed to a web page, but why not compiled to a web page? .html file contains code that needed to be compiled so that it becomes a webpage, right?
Some possible reasons: Maybe when we say something is compiled, it has to be compiled into machine language but .html does not?
HTML does not get compiled - it simply describes how the website should be rendered.
And that is then interpreted by the browser - it doesn't end up as machine code.
It's like a map or blue prints telling the browser's rendering engine how to build the website.
The W3C defines how these "plans" should be written and the browser vendor should make sure they interpret the plans in the correct way.
Developers should make sure they use the HTML elements properly so that the HTML files make sense and the browser can construct the web page properly.
What difference does it make? You have not described a problem you are having.
The parsing of HTML is application-dependent. Each browser/parser decides how to do it.
HTML however must be dynamically modifiable. Since HTML is not executed, it is not clear what the difference is between compiling and interpreting but typically compiled code can't be easily modified.
JavaScript is by definition interpreted.
When i browse my redmine url as http://redmine.mydomain.com it opens download dialogue box and that main page is saved instead of redering html
When i do http://redmine.mydomain.com/login it shows the html code of the login page instead of displaying login page.
It was working fine before 3-4 days. What is wrong all of a sudden? Please help me.
Are you using apache as a proxy?
Make sure you are not modifying the ContentType header with some AddType or Header directive.
On firefox 11 you can open the Web Console (Ctr-Shift-K), open http://redmine.mydomain.com/login and see the Content-Type of the response.
You should be receiving something like: Content-Type:text/html; charset=utf-8.
You can also try making the request directly to your rack server, if you're using thin or mongrel, and see if you also get the same Content-Type.
I need to embed Vaadin app in a third party web page.
Web server and application server are in different domains.
Due to the nature of the application, using iframe is not an option. So I used VaadinXS add-on and embeded application inside a div.
Now my problem is:
Web page has non utf encoding (actually it is windows-1251).
And Vaadin servlet default encoding seems to be utf-8.
The question:
Is there a way to override character encoding for Vaadin embedded XS servlet.
In case anyone will face the same problem. I found a solution. View it here
I have a website that displays fine with IE and Firefox.
But the menus are replaced by question marks when using Safari (I have been told, not having Safari on my PC).
Here is the home page (get rid of spaces):
www.v u b r i d g e.com
Any help welcome.
BTW, is there any Safari emulation for Windows based PC?
I don't see any question mark on your web page, even on the French version. If there is a problem, it's an encoding problem. Check that all your files are encoded in iso-8859-1 (the text encoding you declared in the meta html tag on your web page). If they are, then it could be your server that say the client the content is encoded in utf-8 or any other text encoding. In order to fix it, just configure the header content-type and charset to the correct value. (I've seen your website is made out of aspx which I don't know, but in php it would be header("Content-type: text/html; charset=iso-8859-1;");, to be placed before any output)