Question
Areteans
AU
Last activity: 3 Mar 2017 17:14 EST
Unable to extract access group from URL for static content request from request /images/x-sprites.png requestor
Hi Team,
I am getting the following error message frequently in log file of Production environment:
"Unable to extract access group from URL for static content request from request /images/x-sprites.png requestor=H989E2FE4F4FA06284AF57F0A2083A195 referrer"
Can someone please tell me the root cause for this log message.
Thanks & Regards,
Divya Sri Padarthy.
Message was edited by: Marissa Rogers - added category
Accepted Solution
Pegasystems Inc.
AU
Hi Divya, Its a HotFix-8818
Updated: 15 May 2016 13:10 EDT
Pegasystems Inc.
IN
Hi Divya, Good morning!
- I think, system is trying to access an invalid rule of type 'Rule-File-Binary'.
- As it is static content cache we could try clearing from
- browser cache and if error persists
- check the value for http/defaultcachingtimeout setting in prconfig.xml
- on server we need to diagnose staticcontent/.../global [..\Tomcat7063\Temp\StaticContent\autogenerated\Rule-File-Binary] folder to invalidate this file.
- also please confirm if the agent StaticContentCleaner is running or when did the last run happened.
- browser cache and if error persists
- As it is static content cache we could try clearing from
Please share your comments/thoughts, Thank you!
psahukaru
Pegasystems Inc.
AU
Hi Divya,
Could you please mention the PRPC version, we had provided a hotfix for PRPC v6.3.1. If the URL contains asterisk or some special characters like ", ?, *, <, >, |, : , the path of URL is not formed properly and Error in static content path prevents file from being served and hence causing the issue.
Pegasystems Inc.
IN
Hi Divya,
Please find the steps to obtain the HotFix in the article here: Raising Support Requests for Hotfixes now made easy!
Basavaraj Kadakol - Thank you for sharing the hotfix details.
~Vidyaranjan A V | Community Moderator | Pegasystems Inc.
JABIL
US
Hello Friends,
We are seeing this error "Unable to extract access group from URL for static content request" when trying to open the function builder in a report definition. We are using pega 7.1.9 This doesn't happen in development environment , but only staging .
Is the hotfix 8818 applicable to pega 7.1.9 . I believe the error is because of a malformed request url (with any special symbols) . In one other thread , I found commenting below lines in web.xml would fix it. Is that what the hotfix does too?
Comment out the following from web.xml (found in prweb.war within the ear file).
<servlet-mapping>
<servlet-name>WebStandard</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
Hello Friends,
We are seeing this error "Unable to extract access group from URL for static content request" when trying to open the function builder in a report definition. We are using pega 7.1.9 This doesn't happen in development environment , but only staging .
Is the hotfix 8818 applicable to pega 7.1.9 . I believe the error is because of a malformed request url (with any special symbols) . In one other thread , I found commenting below lines in web.xml would fix it. Is that what the hotfix does too?
Comment out the following from web.xml (found in prweb.war within the ear file).
<servlet-mapping>
<servlet-name>WebStandard</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
Appreciate any helpful information . Thanks in advance!
-Santhosh
Areteans
AU
Hi Santhosh,
This issue what we are facing is in PRPC 6.3 sp1.
And the hotfix was working for us.
You can check with support team, whether this hotfix will work for 7.1.9
Thanks,
Divya Sri Padarthy
JABIL
US
Hi Divya,
Thank you for the response. We will check with the support team , but meanwhile could you please let us know the change that is in the hotfix ? I want to try it out in my private edit and see if its going to work.
Thanks Again!
Pegasystems Inc.
IN
Hi Santosh,
Please compare the hotfix inventory of both Staging and Development and check whether there are any hotfixes that are causing the issue.
As per the corresponding Bug item raised for Hfix-8818, this is supposed to be fixed in Pega 7.1.
Let us know the results.
Best Regards,
Mounika