Sunday, January 31, 2021

Uncaught (in promise) TypeError: Failed to execute 'Cache' on 'addAll': Request failed

 Error in Service Worker.

Uncaught (in promise) TypeError: Failed to execute 'Cache' on 'addAll': Request failed.

Main cause of this is typo in one of the filenames/ OR file is not exists that had added to cached_urls. It did not match the name of the real file so I kept getting the error.

I Got this issue due to typo in the filename and found it by quickly setting cached_urls to an empty list and found that the error went away.

Monday, January 25, 2021

Advanced SEO - Separate URLs for Mobile and desktop applications

We can configure Separate URLs for Mobile and desktop applications

Annotations for desktop and mobile URLs

To help Google algorithms understand separate mobile URLs, we recommend using the following annotations:

  1. On the desktop page, add a rel="alternate" tag pointing to the corresponding mobile URL. This helps Googlebot discover the location of your site's mobile pages.
  2. On the mobile page, add a rel="canonical" tag pointing to the corresponding desktop URL.

google support two methods to have this annotation: in the HTML of the pages themselves and in sitemaps. For example, suppose that the desktop URL is http://example.com/page-1 and the corresponding mobile URL is http://m.example.com/page-1. The annotations in this example would be as follows.

Annotations in the HTML

On the desktop page (http://www.example.com/page-1), add the following annotation:

<link rel="alternate" media="only screen and (max-width: 640px)"
 
href="http://m.example.com/page-1">

On the mobile page (http://m.example.com/page-1), the required annotation should be:

<link rel="canonical" href="http://www.example.com/page-1">

This rel="canonical" tag on the mobile URL pointing to the desktop page is required.

Annotations in sitemaps

Google support including the rel="alternate" annotation for the desktop pages in sitemaps like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
 
<url>
   
<loc>http://www.example.com/page-1/</loc>
   
<xhtml:link rel="alternate" media="only screen and (max-width: 640px)"
   
href="http://m.example.com/page-1" />
 
</url>
</urlset>

The required rel="canonical" tag on the mobile URL should still be added to the mobile page's HTML.

Tuesday, January 19, 2021

Plesk - Upgrade the .net Framework to 4.7.2 OR 4.8

 Steps to Upgrade the .net Framework to 4.7.2 OR 4.8

1. First Download the .NET Framework from https://dotnet.microsoft.com/download/dotnet-framework 

2. Install on the Server.

3. Login to the Plesk and go to "Tools & Settings" > "Server Components" and refresh the components using the refresh button



4. After update, it will reflect in "Web Script" section at the server component page.


All done!!!

Tuesday, January 12, 2021

How to split column with delimiter into two columns in SQL Server Split

We can use Case and  CHARINDEX to split column with delimiter into two columns in SQL Server

select 
    case when CHARINDEX('_',name)>0 
         then SUBSTRING(name,1,CHARINDEX('_',name)-1) 
         else name end firstname, 
    CASE WHEN CHARINDEX('_',name)>0 
         THEN SUBSTRING(name,CHARINDEX('_',name)+1,len(name))  
         ELSE NULL END as lastname
from emp

you can use CASE command to control is last name available.


MS SQL Server:

Query 1:

declare @t table (id int, name  varchar(50))

insert into @t (id,name) values( 1    ,'abc_rao')
insert into @t (id,name) values( 2    ,'nani')
insert into @t (id,name) values( 3    ,'hari_babu')
insert into @t (id,name) values( 4    ,'kalibabu')
insert into @t (id,name) values( 5    ,'ab_tan')

select 
    case when CHARINDEX('_',name)>0 
         then SUBSTRING(name,1,CHARINDEX('_',name)-1) 
         else name end firstname, 
    CASE WHEN CHARINDEX('_',name)>0 
         THEN SUBSTRING(name,CHARINDEX('_',name)+1,len(name))  
         ELSE NULL END as lastname
from @t

Results:

| FIRSTNAME | LASTNAME |
|-----------|----------|
|       abc |      rao |
|      nani |   (null) |
|      hari |     babu |
|  kalibabu |   (null) |
|        ab |      tan |


Thursday, January 7, 2021

How to cancel your Zoom subscription or add-ons at anytime?

Cancel a Pro (paid) subscription
  • Sign in to the Zoom web portal.
  • Click Account Management, then click Billing.
  • Under the Current Plans tab, find the plan you want to cancel and click Cancel Subscription to stop your subscription's automatic renewal.
  • Confirm your request by selecting Cancel Subscription.
  • Choose why you would no longer like to renew your subscription.
  • Once complete, click Submit.
    Your plan status will now be updated to Canceled. You will still have use of your paid plan for the remainder of your subscription term.
  • (Optional) If you would no longer like to have the plan canceled, you will be able to reactivate your plan by selecting Reactivate Plan on the Current Plans page.
Note: If it says Contact Sales instead of Cancel Subscription, you will need to contact our sales team or your Account Executive to have the plan canceled

Tuesday, January 5, 2021

How to set up an HTTP/HTTPS redirect in IIS

In order to force a secure connection on our website, it is necessary to set up a certain HTTP/HTTPS redirection rule. This way, anyone who enters your site using a link like “domain.com” will be redirected to “https://domain.com” or “https://www.domain.com” (depending on your choice) making the traffic encrypted between the server and the client side.

Steps to setup an IIS HTTPS redirect:

  • Download and install the URL Rewrite module.
  • Open the IIS Manager console and select the website you would like to apply the redirection to in the left-side menu:
  • Double-click on the URL Rewrite icon.
  • Click Add Rule(s) in the right-side menu.
  • Select Blank Rule in the Inbound section, then press OK.
  • Enter any rule name you wish.
  • In the Match URL section:
    • Select Matches the Pattern in the Requested URL drop-down menu
    • Select Regular Expressions in the Using drop-down menu
    • Enter the following pattern in the Match URL section: (.*)
    • Check the Ignore case box
  • In the Conditions section, select Match all under the Logical Grouping drop-down menu and press Add.
  • In the prompted window:
    • Enter {HTTPS} as a condition input
    • Select Matches the Pattern from the drop-down menu
    • Enter ^OFF$ as a pattern
    • Press OK
  • In the Action section, select Redirect as the action type and specify the following for Redirect URL:

    https://{HTTP_HOST}{REQUEST_URI}
  • Un-check the Append query string box.
  • Select the Redirection Type of your choice. The whole Action section should look like this:
    NOTE: There are 4 redirect types of the redirect rule that can be selected in that menu:
    • Permanent (301) – preferable type in this case, which tells clients that the content of the site is permanently moved to the HTTPS version. Good for SEO, as it brings all the traffic to your HTTPS website making a positive effect on its ranking in search engines.
    • Found (302) – should be used only if you moved the content of certain pages to a new place *temporarily*. This way the SEO traffic goes in favour of the previous content’s location. This option is generally not recommended for a HTTP/HTTPS redirect.
    • See Other (303) – specific redirect type for GET requests. Not recommended for HTTP/HTTPS.
    • Temporary (307) – HTTP/1.1 successor of 302 redirect type. Not recommended for HTTP/HTTPS.
    OPTION 2: Specify the Redirect Rule as https://{HTTP_HOST}/{R:1} and check the Append query string box. The Action type is also to be set as Redirect.
  • Click on Apply on the right side of the Actions menu.


The IIS redirect can be checked by accessing your site via http:// specified in the URL. To make sure that your browser displays not the cached version of your site, you can use anonymous mode of the browser.

The rule is created in IIS, but the site is still not redirected to https:// Normally, the redirection rule gets written into the web.config file located in the document root directory of your website. If the redirection does not work for some reason, make sure that web.config exists and check if it contains the appropriate rule.

To do this, follow these steps:
  • In the sites list of IIS, right-click on your site. Choose the Explore option:
  • Explore will open the document root directory of the site. Check if the web.config file is there.
  • The web.config file must have the following code block

    <configuration>
     <system.webServer>
     <rewrite>
     <rules>
     <rule name="HTTPS force" enabled="true" stopProcessing="true">
     <match url="(.*)" />
     <conditions>
     <add input="{HTTPS}" pattern="^OFF$" />
     </conditions>
     <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" />
     </rule>
     </rules>
     </rewrite>
     </system.webServer>
    </configuration>


    Note: This is a default configuration. If you'd like to change it, you might need to check this server documentat
    ion
    .
  • If the web.config file is missing, you can create a new .txt file, put the aforementioned code there, save and then rename the file to web.config.