Hello,
I'm observing an odd situation where restlet is involved: pull the net
cable during file upload and router (hardware box, not Router.class)
detects TCP RST attack and blacklist our server for access from subnet.
This is the topology:
- office subnet: client application
- office router: NAT
As an upgrade (Restlet request!), looking through the source code it seems
that the simplest thing would be if I could insert my own ReferenceList
implementation. Perhaps you could have a #setReferenceList option which
would take my own (sub-)class. Not only could I change the HREF, but it
would
Intriguing. Never even occurred to me that something as simplistic as NOT
encoding might work.
This is great, but doesn't mesh nicely with the rest of REST, since of
course what I really want is:
/urls/{url}/foo/bar
And there would be no way to know where the end of the embedded URL was, and
th
I would like to modify the standard Directory to return something different
than "the" file when a file is encountered. For example, peruse a directory
structure (default behavior), but when you get to the "bottom" (an actual
file), then return a report based on that file, instead of the file itse
John D. Mitchell wrote:
For what it's worth...
For production use, I've come to the point where I do *NOT* like
implementing SSL solutions directly in Java. The extra overhead,
hassles, etc. just aren't worth it in general. For example, for both
Krugle and MarkMail, we have SSL (ala HTTPS)
For what it's worth...
For production use, I've come to the point where I do *NOT* like
implementing SSL solutions directly in Java. The extra overhead,
hassles, etc. just aren't worth it in general. For example, for both
Krugle and MarkMail, we have SSL (ala HTTPS) handled directly by th
On Fri, Nov 21, 2008 at 09:44, Tim Peierls <[EMAIL PROTECTED]> wrote:
> Maybe the first line of that FAQ answer should be modified to avoid the word
> "implementation", e.g., "There is a rough correspondence between the MVC
> pattern [cite?] and the Restlet framework:"
I think we can just chang
On Friday 2008.11.21, at 02:35 , Tamás Cservenák wrote:
[...]
Thanks for the tip. That means, that the Application must be aware
that it is fronted by mod_proxy? Is there some possibility (or even
theoretical chance) to have some kind of "fallback" mechanism? Will
look into restlet sources t
Thanks for the feedback Bruno; I'm still learning about certificates and
Restlet, and I appreciate your clarifications!
Regards
Ben
--
From: "Bruno Harbulot" <[EMAIL PROTECTED]>
Sent: Friday, November 21, 2008 2:54 PM
To:
Subject: Re: Well HTTPS
Hi,
I'm not sure you're clear on what certificates, signing and encryption are.
Roughly speaking, an X.509 certificate is the combination of a public
key and some information (subject distinguished name, date from/to,
other attributes) that has been signed using a private key usually
correspo
Hi,
Just started exploring restlet and trying to implement a simple
employee details info management app. it have two pages, one to create a new
employee. second that lists all employees. once the employee is created the
resource should be redirected to other resource which will list all th
Hi,
Ben Johnson wrote:
Hi
I am new to Restlet and web programming, HTTP and SSL certificates in
general, but hopefully my recent experiences will help. I spent the
last several days trying to find a Restlet example using HTTPS (there
isn't one), and eventually pieced together the following
Maybe the first line of that FAQ answer should be modified to avoid the word
"implementation", e.g., "There is a rough correspondence between the MVC
pattern [cite?] and the Restlet framework:"
--tim
On Fri, Nov 21, 2008 at 9:18 AM, Avi Flax <[EMAIL PROTECTED]> wrote:
> Bravo, Rob! I agree 100%!
Bravo, Rob! I agree 100%!
FYI, the FAQ has an entry on MVC:
http://www.restlet.org/documentation/1.1/faq#10
Not sure who wrote the answer, but if you do decide to follow MVC, I think
the approach presented in the answer makes a lot of sense.
Avi
--
Avi Flax » Lead Technologist » Partner » Arc90
This is a purely theoretical observation and not really meant as an answer,
but I did want to sort of get it on the record here.
The MVC paradigm is a specific separation of concerns architecture which has
gained wide conceptual support because it has long been generally considered
best practice fo
salut Thierry,
thanks for your prompt response. my comments are in-line.
On Friday 21 November 2008 03:24:26 am Thierry Boileau wrote:
> Hello Raif,
>
> I have several remarks.
>
> I think you can remove the following parameter which is useless in a
> context of a servlet container (you can see
Thanks, Thierry. I hadn't considered this from an idempotence point of
view, but that makes sense.
Regards
Richard
Thierry Boileau wrote:
> Hello Richard,
>
> after having a look at the HTTP specification
> (http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7), a
> successfull delete o
Sure!
Thanks for the tip. That means, that the Application must be aware that it
is fronted by mod_proxy? Is there some possibility (or even theoretical
chance) to have some kind of "fallback" mechanism? Will look into restlet
sources today...
We already have figured out some means to detect mod_p
Hi Tamas,
Oops, I have to complete my previous answer (looks like I forgot something).
By default, the ClientInfo.getAddress() is based on this instruction (in
HttpClientCall#getLocalAddress):
InetAddress.getLocalHost().getHostAddress().
If this instruction fails (host is unknown for example),
Hi
I am new to Restlet and web programming, HTTP and SSL certificates in general,
but hopefully my recent experiences will help. I spent the last several days
trying to find a Restlet example using HTTPS (there isn't one), and eventually
pieced together the following (using Windows XP SP2 with
Hm,
mod_proxy AFAIK does inserts the 'X-Forwarded-For' HTTP Header, and I am
using the ClientInfo.getAddress() so, if I understand correctly, that
should work correctly, returning always the _true_ client address?
Users are reporting that the Application, when fronted with mod_proxy, is
always
Hello,
there is only one instance of an Application (this principle also
applies to instances of Restlet sub classes) whereas instances of the
Resource class are generated at runtime. One instance of Resource is in
charge to handle one pair of Request/Response.
Generally, the constructor of a
Hello Tamás
the ClientInfo.getAddresses() method relies on the content of the
"X-Forwarded-For" HTTP header. Basically, it contains a coma separated
list of the IPS of the originating client and the intermediate proxies
as follow:
X-Forwarded-For: client1, proxy1, proxy2
The first value of t
23 matches
Mail list logo