Fail to set `Last-Modified' HTTP header - content not cached, bad for reverse proxy
-----------------------------------------------------------------------------------
Key: JBPORTAL-1867
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1867
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.6.3 Final
Environment: Debian, JBoss 4.2.1.GA
Reporter: dpocock
When I request a document from the CMS, there is no HTTP Last-Modified header in the HTTP response.
Therefore, the reverse proxy counts this as a MISS, and fetches the document again. Local proxies and browser caches will also re-fetch every image on every request.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
PostgreSQL Entity Command for jdbc2pm is Not Working Properly
-------------------------------------------------------------
Key: JBAS-5105
URL: http://jira.jboss.com/jira/browse/JBAS-5105
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CMP service
Affects Versions: JBossAS-4.2.2.GA
Environment: PostgreSQL 8.2, Windows XP Pro
Reporter: Dr. Richard Li
Assigned To: Alexey Loubyansky
Priority: Critical
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Merge the unified metadata work
-------------------------------
Key: JBMICROCONT-177
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-177
Project: JBoss MicroContainer
Issue Type: Task
Components: MetaData
Reporter: Scott M Stark
Need to merge the unified metadata work so we can start integrate it into the deployers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
DTD documentation is out of date
--------------------------------
Key: JBPORTAL-1745
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1745
Project: JBoss Portal
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Chris Laprun
This applies to the actual documentation in the DTD but also to the DTD documentation in the reference guide.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Documentation should include a section on how to remove/destroy created objects via the Admin GUI
-------------------------------------------------------------------------------------------------
Key: JBPORTAL-1462
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1462
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Documentation
Affects Versions: 2.6.CR2
Reporter: Chris Laprun
Assigned To: Julien Viet
Fix For: 2.6 Final
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Missing documentation on properties?
------------------------------------
Key: JBPORTAL-1521
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1521
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Documentation
Affects Versions: 2.6 Final
Reporter: Chris Laprun
Assigned To: Julien Viet
Fix For: 2.6.1 Final
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
URL hacking allows edit mode in weather portlet
-----------------------------------------------
Key: JBPORTAL-1841
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1841
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.3 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Priority: Critical
If you are not logged in then weather portlet does not show edit icon which is good. But if I hack the URL to http://localhost:8080/portal/auth/portal/default/Weather/WeatherPortletWi..., I am able to get into edit mode and change the zip code. Is this how it supposed to be?
Sohil suggests:
"no it shouldn't do that. Either the Edit Mode logic of the Portlet should protect against this (a bit painful design), or Portal's security layer should have the granularity to provide role-based protection of the "Edit Mode" of Portlets as a cross cutting aspect. I like the second option better personally"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Security to 2.0.2.Beta3 (from beta and Beta1)
----------------------------------------------
Key: JBAS-5129
URL: http://jira.jboss.com/jira/browse/JBAS-5129
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta4
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Release 2.0.2.Beta4
-------------------
Key: SECURITY-112
URL: http://jira.jboss.com/jira/browse/SECURITY-112
Project: JBoss Security and Identity Management
Issue Type: Task
Security Level: Public (Everyone can see)
Components: RELEASE
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0.2-BETA4
Release 2.0.2.Beta4 of spi and jbosssx along with identity and acl.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira