Thanks everyone for your input. This turned out not to be a HTTP vs. HTTPS
issue. It is related to a mis-configuration of the SSO solution on our
production web site that happened to be using HTTPS. Even after we turned
off HTTPS, the problem initially persisted. Once we re-did the
configuration, the problem went away.
Eric
Keith Bottner-5 wrote:
>
> I needed to make sure that my secure pages were working so I have been
> using the @Secure and then I just installed a self-signed certificate
> into Tomcat. Then I had to make one change so that the ports would be
> set properly by Tapestry, here it is.
>
> public static void contributeAlias(Configuration<AliasContribution>
> configuration,
> @Inject @Value("${"+SymbolConstants.PRODUCTION_MODE+"}" ) final
> String production
> {
> if (0 != production.compareToIgnoreCase("true"))
> {
> BaseURLSource source = new BaseURLSource()
> {
> public String getBaseURL(boolean secure)
> {
> String protocol = secure ? "https" : "http";
>
> int port = secure ? 8443 : 8080;
>
> return String.format("%s://localhost:%d", protocol,
> port);
> }
> };
>
> configuration.add(AliasContribution.create(BaseURLSource.class,
> source));
> }
> }
>
> This is a alternate approach and you may or may not like it better.
>
> Keith
>
> On Nov 13, 2008, at 9:52 AM, natamah wrote:
>
>>
>> Eric,
>>
>> I found a way around this, by adding a method to AppModule.java under
>> com.db.dbiq.services.
>>
>> public void
>> contributeMetaDataLocator(MappedConfiguration<String,String>
>> configuration)
>> {
>> if (HttpHelper.isProduction()) {
>> configuration.add(MetaDataConstants.SECURE_PAGE, "true");
>> }
>> else {
>> configuration.add(MetaDataConstants.SECURE_PAGE, "false");
>> }
>> }
>>
>> In my case, the production sites are secure and the development ones
>> are
>> not. You can substitute HttpHelper.isProduction() with some
>> relevant code.
>>
>> There is also a way to secure individual pages by adding the @Secure
>> notation but my local testing got
>> disturbed when I used this notation.
>>
>> Hope this helps.
>>
>> Mahesh.
>>
>>
>>
>> Eric Ma wrote:
>>>
>>> Running version 5.0.15.
>>>
>>> Form submission works well in HTTP. Under HTTPS, T5 complains
>>> "Error:
>>> Forms require that the request method be POST and that the t:formdata
>>> query parameter have values.".
>>>
>>> It seems 5.0.15 introduced a feature to block form GET. See
>>> https://issues.apache.org/jira/browse/TAPESTRY-2563.
>>>
>>> Any suggestions how to work around this?
>>>
>>> Thanks,
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-T5--Form-submission-via-POST-and-problem-under-HTTPS-tp19925747p20481672.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/-T5--Form-submission-via-POST-and-problem-under-HTTPS-tp19925747p20509370.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
