[ 
https://issues.apache.org/jira/browse/OFBIZ-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040006#comment-17040006
 ] 

Jacques Le Roux commented on OFBIZ-9198:
----------------------------------------

Backported in R17 and R18

> Missing file results in error
> -----------------------------
>
>                 Key: OFBIZ-9198
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9198
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: ecommerce
>    Affects Versions: Release Branch 13.07, Trunk, Release Branch 15.12, 
> Release Branch 16.11
>            Reporter: Ingo Wolfmayr
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: 17.12.01, 16.11.02
>
>         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 a loop.
> Demo data:
> {code:xml}
> <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"/>
> {code}
> 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
(v8.3.4#803005)

Reply via email to