My ISP updated there server last week.
My Actinic V6 site that's was working is now not.
Product menu items links to an error page
IE "You might not have permission to view this directory or page using the
credentials you supplied."
and Fire Fox "
Forbidden
You don't have permission to access /cgi-bin/bb000003.pl on this server. "
ISP comments are "Your scripts appear to be using invalid URLs which is why you are getting the access denied errors on screen. Here is the URL one script appears to try and use:
/cgi-bin/bb000003.pl?ACTINIC_REFERRER=http://66.165.76.200/cgi-bin/bb000003.pl&PRODUCTPAGE=Sheridan_Specialties_JELLY_PASTE_SAUCE_2.html
The issue is with the ":" character, as it is not allowed to appear in such a manner. It must be "encoded" to look like %3A since the ":" character is a reserved special character and can only be used unencoded for it's reserved purpose (which is separating a username from a password at the beginning of a URL). These security measures were put in place last week due to increased hacker attacks on sites/scripts that were vulnerable to several different types of exploits (which is why it worked prior to that)."
Is there an upgrade to Actinic v6 or a work around.
Thanks
My Actinic V6 site that's was working is now not.
Product menu items links to an error page
IE "You might not have permission to view this directory or page using the
credentials you supplied."
and Fire Fox "
Forbidden
You don't have permission to access /cgi-bin/bb000003.pl on this server. "
ISP comments are "Your scripts appear to be using invalid URLs which is why you are getting the access denied errors on screen. Here is the URL one script appears to try and use:
/cgi-bin/bb000003.pl?ACTINIC_REFERRER=http://66.165.76.200/cgi-bin/bb000003.pl&PRODUCTPAGE=Sheridan_Specialties_JELLY_PASTE_SAUCE_2.html
The issue is with the ":" character, as it is not allowed to appear in such a manner. It must be "encoded" to look like %3A since the ":" character is a reserved special character and can only be used unencoded for it's reserved purpose (which is separating a username from a password at the beginning of a URL). These security measures were put in place last week due to increased hacker attacks on sites/scripts that were vulnerable to several different types of exploits (which is why it worked prior to that)."
Is there an upgrade to Actinic v6 or a work around.
Thanks
Comment