Hi,
I'm trying to install tomcat service for Windows 7 manually on my system
through command prompt.
I tried with">>service.bat install MyProject" but it looks like service
doesn't get installed properly because I can see the service in the list
but when I start it, it throws error.
Any idea on
ssed it, then
this has all been a fun diversion. Ha, ha. Nothing to see here. Move along
now.
> One of the sources of confusion at the beginning of this thread was that
> you were calling this data "params in the header" which mud
b35d32f-714d-4393-
> b8c2-
> b4805e0c7a13&facebookName=bozo.the.clown&twitterName=i.am.bozo&flickrName=bozos.circus&linkedinName=mr.clown.to.you
> HTTP/1.x 201 Created
> Content-Length: 82
> Content-Type: text/plain; charset=UTF-8
> X-Lift-Version: 1.1-M4
> Ser
ady been made and, to my mind, refuted, and
wasting the list's bandwidth.
>> I can find no justification in RFC 2616 for stripping
>> this line out -- it is part of the entity-headers as mentioned above,
>> and
>> the RFC also discusses transparency, stating that hea
tion (always a pain) and no
breaking changes to the API. Am I missing something?
I really appreciate your professionalism and your thoughtful response to
my email despite my obvious frustration. I am glad we were able to resolve
the issue to the benefit of all, and I apologize for my earlier testiness.
I should not have rushed to judgment before all the options were
exhausted.
Chas.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
this is probably an uphill battle,
and I can just switch to Jetty. I think it would be a very good idea for
Tomcat to do it, though, so if someone here has that kind of pull, by all
means...
And that's all the time I have for this. Good luck with it, and thanks for
your replies.
>> In fact, what is it with this list? Is this the PUT Haters Club?
>
> Mainly, it is your attitude. Given you are speaking to a community that
> provides assistance to other members of the community for free, a less
> argumentative tone would go a long way to help.
Ah. I think I see where the pro
ST -- both POST and PUT send entities to the
server.
I can only presume that this is a "feature" of Tomcat, ergo I won't bother
with a bug report.
Sigh.
Chas.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.
xplaining that parameters passed with a PUT request seem
to be stripped out by Tomcat (though not by Jetty), and asking if this was
a bug or intended behavior?
It's a mystery to me.
Chas.
> On Fri, Feb 5, 2010 at 4:13 PM, wrote:
>
>> PUT /json/members/1b35d32f-714d-4393-b8c2-b480
ne who knows more about Tomcat than I do (probably everyone on
this list) confirms that the headers are actually being stripped, it's all
probably moot.
Chas.
> c...@munat.com wrote:
> ...
>>
>> So for Tomcat to unilaterally strip the entity-headers from a PUT
>> request
&
ually identical to the above, they appear in the request dump.
I may be wrong, but it seems to me that Tomcat is stripping those headers
out, thus forcing me to use POST even though the correct method should be
PUT for what I'm intending.
Chas.
>
> - -chris
> -BEGIN PGP SIGNAT
*quite clear* on the
difference between POST and PUT -- Roy Fielding, et al, did an excellent
job of it.
Can we, finally, let it rest there? (Pun intended.)
Chas.
>> From: c...@munat.com [mailto:c...@munat.com]
>> Subject: Re: [Fwd: Re: Parameters disappear from PUTs]
>>
>>
vs.
POST? Where exactly does it state or even imply that a PUT entity does not
include parameters in the header, while a POST entity does?
So for Tomcat to unilaterally strip the entity-headers from a PUT request
while passing only the optional entity-body seems just, well, wrong to me.
For this reason, I&
Sorry, I checked and it is already "no". I have full control of the
server, albeit it's 2000 miles away...
Chas.
> As a quick check, can you go into /etc/init.d/tomcat6 and at around line
> 68 you'll see:
>
> TOMCAT_SECURITY=yes
>
> If you're allowed t
OK, turns out my brother has wireshark installed. We ran it, and the
packets are definitely getting to the server with the PUT params intact.
So they arrive at the server, but they are missing from the output of the
valve. Does this mean Tomcat is hosed?
I thought maybe I'd test 24 on my laptop, b
>> From: c...@munat.com [mailto:c...@munat.com]
>> Subject: Parameters disappear from PUTs
>>
>> When I load my app into Tomcat 6 (Ubuntu), the form submission works
>> perfectly if I use a POST: the params are definitely received. If I
>> use a PUT, it works, but the parameters are missing
>
> 1)
base. But the row is
blank. (The only required field is the ID and that's passed in the URL.)
I'm stumped. Anyone have any ideas?
TIA,
Chas.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additi
17 matches
Mail list logo
