[jira] [Commented] (ROL-1795) Posting comments with SchemeEnforcementFilter in operation.

["Glen Mazza (JIRA)" <ji...@apache.org>]

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

Glen Mazza commented on ROL-1795:
---------------------------------

Greg this JIRA was created by you in 2009, do you know if this problem still present in trunk?

> Posting comments with SchemeEnforcementFilter in operation.
> -----------------------------------------------------------
>
>                 Key: ROL-1795
>                 URL: https://issues.apache.org/jira/browse/ROL-1795
>             Project: Apache Roller
>          Issue Type: Bug
>          Components: Comments
>    Affects Versions: 5.0
>            Reporter: Greg Huber
>            Assignee: Roller Unassigned
>            Priority: Minor
>
> Hello,
> I have noticed a strange issue when posting comments etc.  If the first URL requested is a login page with the SchemeEnforcementFilter in operation the initFilter incorrectly (?) sets the absolute context url to be an HTTPS rather than HTTP.  This causes strange goings on as the template page urls can contain mixed urls, feeds can contain duplicate entries, and the POST on the comment sometimes does not work, 
> This seems to fix the bug:
> InitFilter  getAbsoluteUrl(..)
> // Check init post
> 		if (request.isSecure()) {
> 			// Someone has requested https: first, so guess what the correct URL is.
> 			url = "http://" + request.getServerName() + request.getContextPath();
> 		} else {
> 			// then just add on the context path
> 			url += request.getContextPath();
> 		}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)