You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2014/09/29 11:20:33 UTC

[jira] [Commented] (FELIX-4657) HTTP SSLFilter wrong port

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

J.W. Janssen commented on FELIX-4657:
-------------------------------------

For completeness, my reply on this on the Felix-dev ML:
{quote}
I'm less inclined to immediately state this as a bug. Though it is by convention to use port 443 for secure HTTP, actually nothing prevents me from using port 80 instead for secure HTTP.
{quote}

> HTTP SSLFilter wrong port
> -------------------------
>
>                 Key: FELIX-4657
>                 URL: https://issues.apache.org/jira/browse/FELIX-4657
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>            Reporter: Antonio Sanso
>
> looking at [FELIX-3693] HTTP SSLFilter pecially at the SslFilterRequest it looks to me that the final Request object might end up having this weird behavior:
> - request.getScheme() ==> https
> - request.getServerPort() ==> 80
> and possibly
> - request.getRequestURL() ==> https://domain.80/active.html
> IMHO having a scheme https with a port 80 might lead to some inconsistencies .
> See also mailing list discussion in [0].
> patch to follow
> [0] http://www.mail-archive.com/dev@felix.apache.org/msg34344.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)