You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2012/12/11 18:55:21 UTC
[jira] [Comment Edited] (FELIX-3814) Javascript error when directly
invoking a configuration with IE8
[ https://issues.apache.org/jira/browse/FELIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529166#comment-13529166 ]
Alexander Klimetschek edited comment on FELIX-3814 at 12/11/12 5:54 PM:
------------------------------------------------------------------------
Setting "cache: false" in the advanced options of jquery post() or ajax() will add a timestamp-based cache killer automatically. http://api.jquery.com/jQuery.ajax/
I am only wondering why $.post does a GET request?
was (Author: alexander.klimetschek):
Setting "cache: false" in the advanced options of jquery post() or ajax() will add a timestamp-based cache killer automatically.
I am only wondering why $.post does a GET request?
> Javascript error when directly invoking a configuration with IE8
> ----------------------------------------------------------------
>
> Key: FELIX-3814
> URL: https://issues.apache.org/jira/browse/FELIX-3814
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-3.1.8, webconsole-4.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: webconsole-4.0.2
>
>
> When requesting a specific configuration directly using IE8 like:
> http://localhost:8080/system/console/configMgr/org.apache.sling.event.impl.jobs.jcr.LockManager
> this results in a javascript error.
> I'Ve traced this a little bit down (or tried to) and it seems that this call in config.js:
> $.post(create ? uri + '?create=1' : uri, null, displayConfigForm, 'json');
> does a GET on IE8 which in turn doesn't return JSON and that results in a parsing error
> (but might also be something completely different)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira