[
https://issues.apache.org/jira/browse/SLING-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil updated SLING-2132:
------------------------
Description:
Comment: I marked this as a major because this is the first thing any potential
user tries when they download the project
Steps to reproduce:
* Install the launchpad jar in a blank directory
* Execute curl -u admin:admin -F"sling:resourceType=foo/bar" -F"title=some
title" http://localhost:8080/content/mynode
* Observe the response:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 404 NOT_FOUND</title>
</head>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /content/mynode. Reason:
<pre> NOT_FOUND</pre></p><hr /><i><small>Powered by
Jetty://</small></i><br/>
According to the "Discover with sling in 15 minutes" this should have created
some content. I had to replace it with:
curl -u admin:admin -F"sling:resourceType=foo/bar" -F"title=some
title" http://localhost:8080/mynode
One very interesting thing about this was that when I had been using Sling for
some time, the curl command worked. I had to re-install a virgin version (by
running the launchpad jar in a clean directory) to recreate the defect. I tried
to recreate the defect in the version I was using, and even deleted the
'content' node, but that made no difference: in the version I had used for a
while the curl command worked, and in the virgin version it didn't
was:
Comment: I marked this as a major because this is the first thing any potential
user tries when they download the project
Steps to reproduce:
* Install the launchpad jar in a blank directory
* Execute curl -u admin:admin -F"sling:resourceType=foo/bar" -F"title=some
title" http://localhost:8080/content/mynode
* Observe the response:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 404 NOT_FOUND</title>
</head>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /content/mynode. Reason:
<pre> NOT_FOUND</pre></p><hr /><i><small>Powered by
Jetty://</small></i><br/>
According to the "Discover with sling in 15 minutes" this should have created
some content. I had to replace it with:
curl -u admin:admin -F"sling:resourceType=foo/bar" -F"title=some
title" http://localhost:8080/mynode
One very interesting thing about this was that when I had been using Sling for
some time, the curl command worked. I had to re-install a virgin version (by
running the launchpad jar in a clean directory) to recreate the defect
> Curl commands in "Discover with sling in 15 minutes" are slightly wrong
> -----------------------------------------------------------------------
>
> Key: SLING-2132
> URL: https://issues.apache.org/jira/browse/SLING-2132
> Project: Sling
> Issue Type: Bug
> Components: Site
> Environment: * Intel Core2 Q8300 @2,5GHz
> * Windows 7 Home Premium (64 bit) with all the latest updates for 11/7/2011
> * jdk1.6.0_24
> * org.apache.sling.launchpad-6-standalone.jar
> Reporter: Phil
>
> Comment: I marked this as a major because this is the first thing any
> potential user tries when they download the project
> Steps to reproduce:
> * Install the launchpad jar in a blank directory
> * Execute curl -u admin:admin -F"sling:resourceType=foo/bar" -F"title=some
> title" http://localhost:8080/content/mynode
> * Observe the response:
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html;
> charset=ISO-8859-1"/>
> <title>Error 404 NOT_FOUND</title>
> </head>
> <body><h2>HTTP ERROR 404</h2>
> <p>Problem accessing /content/mynode. Reason:
> <pre> NOT_FOUND</pre></p><hr /><i><small>Powered by
> Jetty://</small></i><br/>
> According to the "Discover with sling in 15 minutes" this should have created
> some content. I had to replace it with:
> curl -u admin:admin -F"sling:resourceType=foo/bar" -F"title=some
> title" http://localhost:8080/mynode
> One very interesting thing about this was that when I had been using Sling
> for some time, the curl command worked. I had to re-install a virgin version
> (by running the launchpad jar in a clean directory) to recreate the defect. I
> tried to recreate the defect in the version I was using, and even deleted the
> 'content' node, but that made no difference: in the version I had used for a
> while the curl command worked, and in the virgin version it didn't
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
