New issue
Advanced search Search tips

Issue 174253 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2014
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Sign in to add a comment

GET variables skipped on form submits when using webcal protocol

Reported by, Feb 5 2013

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20100101 Firefox/18.0

Example URL:

Steps to reproduce the problem:
1. Create a form, with its target a webcal:// address and method as get
2. Submit the form (with some variables)

What is the expected behavior?
The variables included in the URL, like so


What went wrong?
The variables are skipped completely. The result is:


Did this work before? No 

Chrome version: 24.0.1312.56  Channel: stable
OS Version: OS X 10.8

This makes it impossible or at least difficult to subscribe to dynamically generated web calendars with Chrome. All other browsers work just fine. Chrome is the only one to behave this way.
Labels: Action-FeedbackNeeded
Tried this on MBP Retina 10.8.2 using latest stable build 24.0.1312.57 (Official Build 178923) 

Steps followed:
1. Launch the URL
2. Click on the button Send it (WEBCAL)
3. It opens up the calender application with the following information in the dialog:

Enter the URL of the calender you want to subscribe to.
Calendar URL webcal:// [Given by default]
with Cancel and Subcribe buttons.

Is this expected??

Comment 2 by Deleted ...@, Feb 15 2013

Expected yes, but wanted no.

There is a hidden variable in the form. When using the http address, the result is:

with webcal address, the result should be:


BUT actually the resulting address is:


So the GET variables are missing when the target address starts with webcal://.

Project Member

Comment 3 by, Mar 9 2013

Labels: -Action-FeedbackNeeded Needs-Feedback
Project Member

Comment 4 by, Mar 10 2013

Labels: -Internals-Network Cr-Internals-Network
Status: WontFix
Closing the bug as this is a year old. Please log a new bug if this problem still persists.

Sign in to add a comment