I have a SWF that works on the web but not over an intranet. The SWF loads it's initial XML content by binding to an asmx HTTP handler. Same code - different servers. On the intranet - a right click shows a SWF context menu - but there is no content rendered. IIS is serving up the correct MIME type (swf/flv) so I think it might be a client issue. The problem occurs on IE/Chrome/FF. Have adjusted browser intranet security settings and looked in advanced settings - no joy yet.
problem solved. the SWF is licenced to work on a specific www domain only.
Related
I have an asp.net application deployed on IIS Server located at 10.0.0.74, when
i tried to access it with chrome browser i get an empty or blank webpage.
However if my colleague tries to access it from his computer he get normal webpage with content on it.
It seems really weird to me what might be the problem.
The screen shot below is what the page looks like.
I would appreciate any help
This is not enough to go on, assuming ASP MVC 5 on IIS here are some suggestions.
On your server
Check the following
Is the physical path in IIS correct - actually point to your code?
Do you have any rewrite rules in your web.config that could be redirecting?
Did you set up the bindings correctly?
Are you hitting the site under https / http?
Checked "Turn windows features on/off" and see if ASP.NET 4.8 installed
Did you setup the HTTP Redirection and HTTP Errors
See how you are setting up error handling setup in your global.asax, see here and disable it
Goto your Control panel > Programs and features > Turn Windows features on or off and under "World Wide Web Services" / components:
Common HTTP features:
Default document
Directory browsing
HTTP Errors
HTTP Redirection
Static Content
Security
Basic authentication
Request filtering
URL Authorization
Windows authentication
The problem was that the plugins in "Content" folder were not included in the projects.
I included all the files shown in the image below.
I apologize for wasting your time, i should have checked the console before!
In my quest to get the best performance for an ASP.Net/IIS based web application, I would like to have static content be served up from a cookieless domain as suggested by Google.
I have followed this discussion and understand how it would work. Stopping cookies being set from a domain (aka "cookieless domain") to increase site performance
What I fail to understand is how to have the image/js/css files' src point to the new domain name instead of the one resolved by the browser when served up from the original web application.
Here is what I mean -
Original Web Application in IIS at myapp.mydomain.com
Cookieless Web Application in IIS at static.mydomain.com
img tag in a web page is served to the browser from the original Web Application as src="Images/someimage.jpg" which the browser automatically resolves to myapp.mydomain.com/Images/someimage.jpg
The problem for which I am looking for a simple and a smart solution -
Across the application, how do I get the img and asp:image to serve absolute URLs instead of the relative URLs. i.e. have the img tag get the absolute URL as src="//static.mydomain.com/image/someimage.jpg"
PS: I have also referred to How do I setup IIS with a cookieless domain to improve performance? and lot of similar contents, but all of these are tell you what is to be done, but not the how to implement at the ground level.
You will have to provide the fully qualified url:
src="//static.mydomain.com/image/someimage.jpg"
or
src="http://static.mydomain.com/image/someimage.jpg"
I don't see any other way around it.
I have developed a web project using PowerBuilder V12.0 and it is published in ASP.net web file formats (*.aspx).
I have hosted my web project on a web server machine with operating system (Windows Server 2003 - Enterprise Edition) and IIS V6.0 as Web Server Hosting Application.
I would like to make the home page (Default.aspx) opened maximized so that no internet toolbars appears in the Internet Explorere or any other internet browser like Firefox and so on.
It seems this is a web server configuration and setting as now I host the same web application in two development web servers and it opens maximized in one of them and opens normal in the other so No changes are needed in the web project files.
I do not know exactly what is this option or configuration,, Is there a property like window size or width and height in web configuration files like web.config and machine.config ? I guess there is a property like WindowSize:Maximized.
If you had experience with that before please let me know the options and configurations needed to do that.
Thanks for your help.
You can use JavaScript to resize the browser window but I think it's generally bad form and not always supported. Some browsers won't do it at all, some will block it, etc.
Pretty sure you can't control any other aspects of window display, such as toolbar visibility, etc. Well - you can when opening new browser windows but you can't enforce this on the first load of the page.
http://www.w3schools.com/jsref/met_win_resizeto.asp
Tried it in Chrome, no worky, tried it in IE, you get "IE has restricted this webpage from running scripts..."
I can see why you would want to enforce how your web app is displayed but that's something that's really left to the client.
I set up 404 handler page in web.config, but it works ONLY when extension of URL is .aspx (or other which is handled by ASP.NET).
I know I can setup static HTML page in website options, but I want to have a page.
Is there any options to assign ASPX handler page for all request extensions in IIS?
The direct question was whether or not there are options to assign the ASPX handler to all request extensions: Yes, there is. I'll discuss how to do that shortly.
First, I think the "hidden" question -- the answer you really want -- is whether or not there's a way to redirect all 404 errors for pages other than ASPX, ASMX, etc. Yes, there is, and this is the better choice if it'll solve the issue you're having.
To redirect all 404s in IIS 6, right click your web application root (whether it be its own site or a virtual directory in the main site), and choose "Properties." From there, choose the "Custom Errors" tab. Find 404 in the list and change it to the redirect you want.
Now, if that won't suffice -- and I really hope it does -- yes, you can run every page through the ASPX handler. However, doing so comes at a fairly high cost in terms of efficiency -- raw HTML/image serving is considerably faster than anything dynamic.
To do this, right click your web application root and choose "Properties." Choose the "Home Directory" tab. Click "Configuration;" a new window will pop up. Copy the path from one of the ASP.NET page serves, and then use it for a wildcard application map.
Bear in mind, again, this is the wrong answer most of the time. It will negatively impact your performance, and is the equivalent of using a chainsaw to carve a turkey. I highly recommend the first option over this one, if it will work out for you.
For information:
This is one of the several nice things that IIS7 brings - all pages are routed through the handler such that you can do custom 404s and - usefully - directory and file level security for any file (based on the same web.config stuff as for asp.net files prior to IIS7).
So notionally "use II7" is an answer (will be "the" answer in time) - but of course its not a terribly practical one if you're not hosting/being hosted on W2k8 (or higher).
The web.config can only set up errors pages for pages controlled by it's web site. If you have any other pages outside the purview of the ASP.Net application, then you set up handling for them in IIS. There's an option in there for configuring the 404 page where you can point it to your custom page.
Only other thing i can think of is passing ALL extensions to asp.net.
This way all types of files get processed by asp.net and your custom error page will work.
In the IIS application configuration, you can set a wildcard mapping (".*") to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
You can setup wild card mapping in IIS (Application configuration/Mappings/Wildcard mappings/ - just set aspnet_isapi.dll as executable and uncheck the Verify that file exists box) that will route all incoming requests to your app - so you can control the behavior directly from it.
You don't have to setup static page in your IIS application settings. Imho, you should be able to setup valid url (e.g. /error_handler.aspx) from your app that will be used as landing page in case of specific server error.
In IIS you can set a Custom Error for 404 errors and direct it to a URL in the site properties.
It shows a static html by default
C:\WINDOWS\help\iisHelp\common\404b.htm
You can change it to a relative url on your site.
I have an ASP.NET webforms application (3.5 SP1) that I'm working on, and attempting to enable gzip fpr HTML and CSS that comes down the pipe. I'm using this implementation (and tried a few others that hook into Application_BeginRequest), and it seems to be corrupting the external CSS file that the pages use, but intermittently...suddenly all styles will disappear on a page refresh, stay that way for awhile, and then suddenly start working again.
Both IE7 and FF3 exhibit this behavior. When viewing the CSS using the web developer toolbar, it returns jibberish. The cache-control header is coming through as "private," but I don't know enough to figure out if that's a contributing factor or not.
Also, this is running on the ASP.NET Development Server. Maybe it'd be fine with IIS, but I'm developing on XP and it'd be IIS5.
Is it only CSS files that get corrupted? Do JS files (or any other static text files) come through ok?
Also can you duplicate the behavior if you browse directly to the CSS file?
I've only enabled compression on Windows 2003 server's IIS using this approach:
IIS → Web Sites → Properties → Service tab, check both boxes
IIS → Web Service Extensions → Right click, Add New
Name
Http Compression
Required Files
%systemroot%\system32\inetsrv\gzip.dll
IIS → Right click top node, Internet Information Services, check Enable Direct Metabase Edit
Backup and Edit %systemroot%\system32\inetsrv\MetaBase.xml
Find Location ="/LM/W3SVC/Filters/Compression/gzip"
Add png, css, js and any other static file extensions to HcFileExtensions
Add aspx and any other executable extensions to HcScriptFileExtensions
Save
Restart IIS (run iisreset)
If you have a Windows 2003/2008 server to play with you could try that approach.
If you will be deploying on IIS 6 or IIS 7, just use the built-in IIS compression. We're using it on production sites for compressing HTML, CSS, and JavaScript with no errors. It also caches the compressed version on the server, so the compression hit is only taken once.