ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ingo Wolfmayr (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OFBIZ-9198) Missing file results in infinite loop
Date Thu, 02 Feb 2017 19:45:51 GMT

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

Ingo Wolfmayr updated OFBIZ-9198:
---------------------------------
    Description: 
When accessing a file/image in ecommerce (only seo version) that is physically missing or
the dataresource attribute isPublic=="N" the request results in an infinite loop.

Demo data: 

<Content contentId="test" contentTypeId="DOCUMENT" dataResourceId="test" statusId="CTNT_PUBLISHED"/>
<DataResource dataResourceId="test" dataResourceTypeId="LOCAL_FILE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" dataResourceName="Test Image" objectInfo="PATH TO FILE" isPublic="N"
 />
<Content contentId="testurl" contentTypeId="DOCUMENT" dataResourceId="testurl" statusId="CTNT_PUBLISHED"/>
<DataResource dataResourceId="testurl" dataResourceTypeId="URL_RESOURCE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" objectInfo="/testbild-content" isPublic="N"/>
<ContentAssoc contentId="test" contentIdTo="testurl" contentAssocTypeId="ALTERNATE_URL"
fromDate="2006-09-22 00:00:00.0"/>

Call:
/ecomseo/testbild-content
/ecomseo/stream?contentId=test

I found that because I had server problems (server down), so it is quite easy to kill the
server by streaming a not existing contentId via via the ecomseo app.

/ecomseo/stream?contentId=test1

  was:
When accessing a file/image in ecommerce (only seo version) that is physically missing or
the dataresource attribute isPublic=="N" the request results in an infinite loop.

Demo data: 

<Content contentId="test" contentTypeId="DOCUMENT" dataResourceId="test" statusId="CTNT_PUBLISHED"/>
<DataResource dataResourceId="test" dataResourceTypeId="LOCAL_FILE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" dataResourceName="Test Image" objectInfo="PATH TO FILE" isPublic="N"
 />
<Content contentId="testurl" contentTypeId="DOCUMENT" dataResourceId="testurl" statusId="CTNT_PUBLISHED"/>
<DataResource dataResourceId="testurl" dataResourceTypeId="URL_RESOURCE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" objectInfo="/testbild-content" isPublic="N"/>

Call:
/ecomseo/testbild-content
/ecomseo/stream?contentId=test

I found that because I had server problems (server down), so it is quite easy to kill the
server by streaming a not existing contentId via via the ecomseo app.

/ecomseo/stream?contentId=test1


> Missing file results in infinite loop
> -------------------------------------
>
>                 Key: OFBIZ-9198
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9198
>             Project: OFBiz
>          Issue Type: Bug
>          Components: specialpurpose/ecommerce
>    Affects Versions: Release Branch 13.07, Trunk, Release Branch 15.12, Release Branch
16.11
>            Reporter: Ingo Wolfmayr
>            Priority: Critical
>         Attachments: errror.txt
>
>
> When accessing a file/image in ecommerce (only seo version) that is physically missing
or the dataresource attribute isPublic=="N" the request results in an infinite loop.
> Demo data: 
> <Content contentId="test" contentTypeId="DOCUMENT" dataResourceId="test" statusId="CTNT_PUBLISHED"/>
> <DataResource dataResourceId="test" dataResourceTypeId="LOCAL_FILE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" dataResourceName="Test Image" objectInfo="PATH TO FILE" isPublic="N"
 />
> <Content contentId="testurl" contentTypeId="DOCUMENT" dataResourceId="testurl" statusId="CTNT_PUBLISHED"/>
> <DataResource dataResourceId="testurl" dataResourceTypeId="URL_RESOURCE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" objectInfo="/testbild-content" isPublic="N"/>
> <ContentAssoc contentId="test" contentIdTo="testurl" contentAssocTypeId="ALTERNATE_URL"
fromDate="2006-09-22 00:00:00.0"/>
> Call:
> /ecomseo/testbild-content
> /ecomseo/stream?contentId=test
> I found that because I had server problems (server down), so it is quite easy to kill
the server by streaming a not existing contentId via via the ecomseo app.
> /ecomseo/stream?contentId=test1



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message