Is there a recommended way, within Wicket, to move a user from HTTP to HTTPS for one or several pages, then move them back to HTTP? This is handled within Struts by the SSLEXT package. Thanks for your time.
Martijn, grab the G4 optimized version of Firefox ... I've been a
staunch supporter of safari on my powerbook for over a year and a
half .. and this optimized version, called DeerPark i think ... rocks
On Dec 5, 2005, at 10:56 PM, Martijn Dashorst wrote:
Just for the record, Google's back
I don't know. What is the main problem you are having (hard coding
url's probably), and do you have an idea of how support should look
like? For instance, would it (ssl/ normal) be something you could
configure your page maps with?
Any other people been doing this? How do competing frameworks
I'd like to either see something like WebPage.isSecure() or WebPage.getScheme(), like Christian suggested. I don't think redirecting to an HTTPS page would work in checkAccess() because I believe form properties from a POST would be lost.
On 12/6/05, Christian Essl [EMAIL PROTECTED] wrote:
There
I just finished more advanced browser/ client capabilities detection.
If anyone wants to take a look at it, I added an example in
wicket-examples called HelloBrowser. It uses Javascript to detect
browser properties, but it has a fallback in case javascript is not
supported (e.g. because of
I'm a bit tied up at the moment, but patches would be welcome :)
Eelco
On 12/6/05, Nick Heudecker [EMAIL PROTECTED] wrote:
I'd like to either see something like WebPage.isSecure() or
WebPage.getScheme(), like Christian suggested. I don't think redirecting to
an HTTPS page would work in
As far as I know all Change(s) get recorded through the component in thePage's versionManager which on the automatic version rewinde just executes
all the Change.undo(). Where the Change comes from, what it does and howit get's there is not important. IMO it would work for Models as forComponents
So to summarize your idea it would be like thisclass SingleSortState IChangeRecorder recorder; SortState(IChangeRecorder) {...} setPropertyState(...) { recorder.addChange( new Change() {...} )
}OrderByLink { onclick () { getState().setProperty(...); } }this has the same net affect as OrderByLink
On 12/6/05, Nick Heudecker [EMAIL PROTECTED] wrote:
I don't think redirecting to
an HTTPS page would work in checkAccess() because I believe form properties
from a POST would be lost.
Unless you redirect with 307 which is supported by modern browsers
(umm, differently). But in this case the
Okay. I'm guessing this would impact WebPage and possibly the Link class. Anything else you think I should look at?On 12/6/05, Eelco Hillenius
[EMAIL PROTECTED] wrote:I'm a bit tied up at the moment, but patches would be welcome :)
EelcoOn 12/6/05, Nick Heudecker [EMAIL PROTECTED] wrote: I'd like
I'd take a look at Page.urlFor()-urlPrefix().
However I do not know how this plays together with the new refactorings.
Christian
On Tue, 6 Dec 2005 15:37:24 -0600, Nick Heudecker [EMAIL PROTECTED]
wrote:
Okay. I'm guessing this would impact WebPage and possibly the Link
class.
Anything
I LOVE this community!
Always get great replies, even for simple things. Thanks!
Comments inline.
My goal is to have a different css page depending on the l10n,
client type, or perhaps other requirements. This is my border:
The wicket:head tag exists for a different reason. You can
I'll add this to the wiki to try to make it a bit clearer
for others, too.
Updated the wiki.
http://www.wicket-wiki.org.uk/wiki/index.php/JavaScript
Would be great if others could verify the accuracy of the contents.
Cheers,
Dave
13 matches
Mail list logo
