Thanks Martin!
https://issues.apache.org/jira/browse/WICKET-4338
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/how-to-get-https-port-number-in-Wicket-1-5-tp4295139p4301617.html
Sent from the Users forum mailing list archive at Nabble.com.
-
Looking at the impls of
org.apache.wicket.request.mapper.parameter.IPageParametersEncoder#decodePageParameters
we can see that only QueryParameters are read.
I personally don't know what is the reason for that.
File a ticket and if no one says that this is the intended behavior
then we will fix it
Hmm, I spoke too soon.
It seems that the reason I was running into the *method* mismatch (not
*protocol* mismatch) with the StatelessForm is due to having installed an
HttpsMapper in my WicketApplication. If you try to post a form over https
from an http page, the HttpsMapper apparently discards
Hi Martin, thanks.
I've already got a solution (from Igor's book mostly, but updated for 1.5)
on how to submit a form over https when the page hosting the form is http. I
was just looking for a way to determine the https port without hard-coding a
reference to WicketApplication. I guess it's not t
See
http://www.petrikainulainen.net/programming/tips-and-tricks/wicket-https-tutorial-part-three-creating-a-secure-form-submit-from-a-non-secure-page/
On Sun, Jan 15, 2012 at 10:51 AM, Per Newgro wrote:
> Thanks for testing this out. I wasn't aware of that.
>
> I didn't understand the usecase ex
Thanks for testing this out. I wasn't aware of that.
I didn't understand the usecase exactly. You want to set the page /
request secure
if you've added the login form? Or do you want to secure the form only.
For the later a possible answer is this
http://stackoverflow.com/questions/96164/partia
Hi Per,
The documentation for @RequireHttps implies that it only works for pages,
not components, and my (limited) testing shows that to be the case. Is there
a way to use it with components on otherwise insecure pages?
My use case is to secure a form on non-https pages, specifically to secure
th
Stupid = my question not yours :-). Only for clearify it :-)
Am 14.01.2012 19:05, schrieb Per Newgro:
Stupid question. Is @RequireHttps at Form class working?
Cheers
Per
Am 14.01.2012 17:44, schrieb armhold:
Assuming that the http/https port number have been set in
WicketApplication
with the
Stupid question. Is @RequireHttps at Form class working?
Cheers
Per
Am 14.01.2012 17:44, schrieb armhold:
Assuming that the http/https port number have been set in WicketApplication
with the following:
setRootRequestMapper(new HttpsMapper(getRootRequestMapper(), new
HttpsConfig(8080,
Assuming that the http/https port number have been set in WicketApplication
with the following:
setRootRequestMapper(new HttpsMapper(getRootRequestMapper(), new
HttpsConfig(8080, 8443)));
... is there any way to get access to the port numbers from components? One
obvious solution is some
10 matches
Mail list logo