[jira] Commented: (WICKET-1883) Refactor some constants in WebRequestCodingStrategy

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641424#action_12641424 ] 

Igor Vaynberg commented on WICKET-1883:
---------------------------------------

i dont get this, even after you change the constants it is still easy to tell you are using wicket if you have urls like

?foo:bar=:34:path.to.component:::

people who are concerned with security should use crypted url coding strategy to make all their urls look like this

?x=987DASD7ASD7AS9D7AS8AS8AS79SA7D9AS79AS7DAS798S7ASD


> Refactor some constants in WebRequestCodingStrategy
> ---------------------------------------------------
>
>                 Key: WICKET-1883
>                 URL: https://issues.apache.org/jira/browse/WICKET-1883
>             Project: Wicket
>          Issue Type: Wish
>          Components: wicket
>            Reporter: Kirill Balyasnikov
>            Priority: Trivial
>
> I'm new to Wicket but as i see many people would like to hide the fact they are using the framework due to security reasons. At this time wicket expose some of it's internal structure via url's containing "wicket:", "interface" and others. These strings are declared constants in WebRequestCodingStrategy:
> public static final String NAME_SPACE = "wicket:";
> public static final String INTERFACE_PARAMETER_NAME = NAME_SPACE + "interface";
> public static final String BEHAVIOR_ID_PARAMETER_NAME = NAME_SPACE + "behaviorId";
> public static final String BOOKMARKABLE_PAGE_PARAMETER_NAME = NAME_SPACE + "bookmarkablePage";
> I propose to transform these constants to simple properties like:
> setNameSpace()
> setInterfaceParameterName()
> setBehaviorIdParameterName()
> As it seems to me such simple refactoring will not break backward compatibility with previous versions of Wicket.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.