[jira] [Updated] (OFBIZ-13071) Could not find PortalPage with portalPageId []

["Jacques Le Roux (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OFBIZ-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux updated OFBIZ-13071:
------------------------------------
        Fix Version/s: 18.12.13
                           (was: Upcoming Branch)
    Affects Version/s: 18.12.12
                           (was: Upcoming Branch)

> Could not find PortalPage with portalPageId [] 
> -----------------------------------------------
>
>                 Key: OFBIZ-13071
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13071
>             Project: OFBiz
>          Issue Type: Bug
>          Components: sfa
>    Affects Versions: 18.12.12
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: 18.12.13
>
>
> This is a weird behaviour. Yet it's not really a bug but something that spider bots do. They get to ListTimezones while not being signed in (hard for spider bot). Here are 2 cases:
> {noformat}
> 18.224.149.242 - - [26/Apr/2024:03:20:05 +0000] "GET /sfa/control/setSessionTimeZone?tzId=Australia/Melbourne HTTP/1.1" 200 42716 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
> 2024-04-26 03:20:05,254 |-0.0.0.0-8009-exec-4 |ModelScreenWidget             |E| Could not find PortalPage with portalPageId [] 
> 3.144.172.115 - - [26/Apr/2024:03:32:22 +0000] "GET /sfa/control/setSessionTimeZone?tzId=Asia/Kuwait HTTP/1.1" 200 42716 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
> 2024-04-26 03:32:22,395 |-0.0.0.0-8009-exec-7 |ModelScreenWidget             |E| Could not find PortalPage with portalPageId [] 
> {noformat}
> It happens only for SFA. [All the others| https://s.apache.org/gwyw2 ] are not concerned
> Why only SFA is concerned is unclear but not really a problem. Because once signed in the problem dissapears. The only problem is that if a spider bot gets to your production server it will clutter the log. There is 636 possible hours...
> Now that I know the reason, I'll try to find a workaround.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)