|
X-UA-Compatible
|
|
30.8.2009 16:43:40
- Filed under :
C#
|
Asp.net
|
CSS
|
AJAX
|
|
|
Implementing the HTTP header is beneficial if a site owner wants most of their site to render as it did in IE7 or if there are no plans to update site content. Inclusion of this header honors any Quirks mode pages that belong to the site. Use below statement at top of your page :
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> or use it in web.config :<system.webServer>
<httpProtocol>
<customHeaders>
<add name="X-UA-Compatible" value="IE=EmulateIE7" />
</customHeaders>
</httpProtocol>
</system.webServer> Using the meta-tag on a per-page basis is beneficial when the publisher wants to opt-in specific pages to render as they did in IE7.
NOTE: The X-UA-Compatible tag and header override any existing DOCTYPE. Also, the mode specified by the page takes precedent over the HTTP header. For example, you could add the EmulateIE7 HTTP header to a site, and set specific pages to display in IE8 mode (by using the meta-tag with content=”IE8”).
Using the IE=EmulateIE7 compatibility tag is a simple way for users to continue their current experience when browsing your site until you can update with more standards-compliant content. Although adding this tag will prevent most display issues, you may also need to update your site to properly detect IE8.
Keywords : Emulate IE7
|
with 0 comments
|
|
|
No buffer space available Fix
|
|
29.8.2009 12:08:04
- Filed under :
C#
|
Asp.net
|
Misc
|
SQL
|
|
|
Error : An operation on a socket could not be performed because the
system lacked sufficient buffer space or because a queue was full
xxxx.xxxx.xxxx:80
Solution 1 :
I think I've found a reason for it: My anti-virus scanner, NOD32
v2.51.12 x64, with enabled HTTP scanning. If the HTTP scanning on port
80,8080,3128 and "Auto Detect HTTP communication on other ports" is
enabled, both versions will crash. After I disabled the IMON (Internet
Monitor) and EMON (MS Outlook E-Mail Monitor) features in NOD32
everything seems to work fine.
Solution 2 :
Editting the registry is not for beginners, if you don't know what
you're doing I suggest you don't try this, basically it's use at your
own risk. Anytime you want to edit the registry it is a good idea to
back it up first..
If you are using Windows 95/98/Me follow these steps:
First
step is to launch the registry editor. To do this go to Start, Run and
type regedit. In the left pane navigate to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP once
there, look for an entry called MaxConnections. If it exists highlight
it by clicking it and then right click it and select modify. Increase
the value (recommended value is to double the current value).
If
the MaxConnections entry does not exist you must create it. To do this,
right click in the right pane and choose new from the menu and select
String Value. Give it the name MaxConnections. Then right click it and
select modify and enter a value of 800.
Restart your computer,
if all goes well then you fixed the problem, if not, revert the changes
by restoring the registry. (You may have to reboot to safe mode to do
this).
If you are running Windows NT/2000/XP follow these steps:
First step is to launch the registry editor. To do this go to Start,
Run and type regedit. In the left pane navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
once there, you must create the entry TcpNumConnections. To do this,
right click in the right pane and choose new from the menu and select
DWORD Value. Give it the name TcpNumConnections. Then right click it
and select modify and enter a value of 800.
Restart your
computer, if all goes well then you fixed the problem, if not, revert
the changes by restoring the registry. (You may have to reboot to safe
mode to do this).
Consideration :
TIP 1 :
I have seen NOD32 cause WSAENOBUFS (10055) on many systems. They seem
to do something which lowers the resources available to networking
applications.
TIP 2 : Problem is caused by a recent windows patch.
If you remove patch KB948609 the client side deserialization will
except large datasets again.
TIP 3 : If an application performs many
network connections simultaneously or within a short window of time,
the application developer might need to increase this number and reduce
the TcpTimedWaitDelay value to avoid receiving a WSAENOBUFS (10055)
error: "An operation on a socket could not be performed because the
system lacked sufficient buffer space or because a queue was full."
(http://msdn.microsoft.com/en-us/library/ms819739.aspx)
Keywords : WSAENOBUFS, 10055
|
with 0 comments
|
|
|
Activate current link in master page
|
|
14.7.2009 13:21:42
- Filed under :
Asp.net
|
CSS
|
|
|
Step 1 :
<ul>
<li id="<%=current("/Index.aspx,/Contact.aspx") %>">
<a href="/Public/CustomerCare/Index.aspx"><span>Customer</span></a></li>
<li id="<%=current("/Contact.aspx") %>">
<a href="/Public/CustomerCare/Contact.aspx"><span>İletişim</span></a></li>
</ul>
Step 2 :
protected string current(string currentpage)
{
// activate current link
string pname = Request.ServerVariables["SCRIPT_NAME"];
string result = pname.Substring(pname.LastIndexOf("/"), pname.Length - pname.LastIndexOf("/"));
if (currentpage.IndexOf(result)>=0)
{
result = "current";
}
return result;
}
Keywords : CSS, activate current page, asp.net
|
with 0 comments
|
|
|
Sorenson Squeeze for reducing .flv files
|
|
27.6.2009 22:32:09
- Filed under :
Asp.net
|
Misc
|
|
|
For starters, Sorenson Media has been the global leader in video encoding and compression technology for nearly a decade and a half.
What does that mean? It means that every day thousands of people rely on Sorenson Media for all their video encoding, publishing and delivery needs. So then the question becomes: Why wouldn't you?
When quality counts, turn to the company you can trust, turn to Sorenson Media.
Raw, uncompressed video is a huge beast. Traditionally, getting it online meant sending any large, foreboding video to the unknown server in the sky so they can encode and deliver to you when they got around to it. This takes up resources, bandwidth and most importantly time. Oh yeah, and it can cost a lot of money.
Utilizing Sorenson's desktop and web-based applications you can compress that video down to a manageable size, upload it to the web and publish to your site in a matter of minutes.
This is my experience steps for reducing size of flv file :
- Get .flv file with "Import File"
- Select "Format Sort" in "Audience presents"
- Select "Adobe Flash Video (.flv)" at line third
- You can choose "F8_256K" to best performance (according to my experience)
- Click "Apply" button to apply filter
- Click "Squeeze it!" at right bottom side of screen to start conversion.
- You can access converted file at directory that original file already located.
Keywords : Reducing .flv video file without loss of quality. Sorenson Squeeze v5.0
|
with 0 comments
|
|
|
Configuring Awstats for Mulitple web sites
|
|
26.6.2009 14:44:33
- Filed under :
Asp.net
|
|
|
I explained something about installation Awstats log analyzer tool before. I list all required steps to implement much more web site to use Awstats report. Here we go :
1. Configure W3SVC log format in IIS (in Website tab)
You should delete all previos log file in Log files directory (ex: C:\WINDOWS\system32\LogFiles\W3SVC129507843) If you can not delete anything in that folder, please try to stop website and delete it again. Then set these properties to enable.
- Date (date)
- Time (time)
- Client IP Address (c-ip)
- Username (cs-username)
- Method (cs-method)
- URI Stem (cs-uri-stem)
- URI Query (cs-uri-query)
- Protocol Status (sc-status)
- Bytes Sent (sc-bytes)
- Protocol Version (cs-version)
- User Agent (cs(User-Agent))
- Referrer (cs(Referrer))
2. Access to web site with Internet explorer/firefox to create sample log file in server's LogFiles directory.
3. Create configuration file in "C:\perl\wwwroot\cgi-bin" (ex : awstats.www.sampledomain.com.tr.conf)
4. Update 3 parameters according to new site.
- LogFile="C:\WINDOWS\system32\LogFiles\W3SVC129507843\ex%YY-24%MM-24%DD-24.log"
- SiteDomain="www.sampledomain.com.tr"
- HostAliases="sampledomain.com.tr www.sampledomain.com.tr"
5. Copy icon folder in "C:\perl\wwwroot\icon" to your root website directory (ex: C:\Inetpub\wwwroot\sampledomain\sampledomain)
6. Create stats folder in web root to publish report (ex : C:\Inetpub\wwwroot\sampledomain\sampledomain\stats)
7. Right click on the stats folder in IIS and select properties, then click documents tab and add default html page name (ex : awstats.www.sampledomain.com.tr.html) Then, move it to first line.
6. Create batch file with following lines (ex : AwstatsService.bat)
C:\Perl\wwwroot\cgi-bin\awstats.pl -config=www.sampledomain.com.tr –update
C:\Perl\tools\awstats_buildstaticpages.pl -config=www.sampledomain.com.tr -update -lang=en -dir="C:\Inetpub\wwwroot\sampledomain\sampledomain\stats" -awstatsprog="C:\Perl\wwwroot\cgi-bin\awstats.pl"
Hint : This batch file use previous day log records. see 9th line below if you want to see current traffic.
7. Create scheduled task in Control Panel for batch file (AwstatsService.bat) to run it in anytime.
8. You can access report by http://www.sampledomain.com.tr/stats/
9. Use this batch file (ex : AwstatsCurrent.bat) if you want to see current usage in traffic report.
C:\Perl\wwwroot\cgi-bin\awstats.pl –config=www.sampledomain.com.tr –update –logfile="C:\WINDOWS\system32\LogFiles\sampledomain\W3SVC1370046439\ex090620.log"
C:\Perl\tools\awstats_buildstaticpages.pl -config=www.sampledomain.com.tr -update -lang=en -dir="C:\Inetpub\wwwroot\sampledomain\sampledomain\stats" -awstatsprog="C:\Perl\wwwroot\cgi-bin\awstats.pl"
Because AwstatsService.bat (in 6th item) use previous day log records.
Note : You should change logfile name that end of first line everyday. (ex090620.log)
10. Note : Don't run batch file (ex : AwstatsCurrent.bat) in 2 minutes again.
Keywords : Awstats configuration for multiple web sites.
|
with 0 comments
|
|
Previous
|
Next
Current Page: 2
|
|