You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2005/02/21 07:57:51 UTC

[jira] Resolved: (BEEHIVE-193) SharedFlow (.jpfs) files should not be web-addressable

     [ http://issues.apache.org/jira/browse/BEEHIVE-193?page=history ]
     
Rich Feit resolved BEEHIVE-193:
-------------------------------

     Resolution: Fixed
    Fix Version: V1Beta

Fixed with revision 154639.  Note that you'll need the latest web.xml (from the webapp template) to see the fix.

> SharedFlow (.jpfs) files should not be web-addressable
> ------------------------------------------------------
>
>          Key: BEEHIVE-193
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-193
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Windows XP, tomcat 5.0.25.
>     Reporter: Alejandro Ramirez
>     Assignee: Rich Feit
>      Fix For: V1Beta

>
> 1.- Deploy a beehive enabled webapp that contains a sharedFlow.  (e.g, you can deploy the coreWeb webapp under //beehive/trunk/netui/test/webapps/drt).
> 2.- Access the sharedflow directly (E.g. http://localhost:8080/coreWeb/pageFlowCore/sharedFlow/hasSharedFlow1/SharedFlow1.jpfs).
> Expected:  The sharedflow should not be web-addressable.
> Actual:  The user gets the actual code of the sharedFlow.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira