Anyway I never though names would be a problem in a non official unit...
Official or not, function names should reflect the propose, or readers
will fail to find it, of find wrong code for what they are looking for.
Anyway, I was just digging to see if something else was behind this
incorrec
The Xml names are there because I started from the example posted by Anton
and I didn't want to create confusion with the existing
HTMLEncode/HTMLDecode function already existing.
Anyway I never though names would be a problem in a non official unit...
The HTTPApp-HTMLDecode function only works fo
Hello,
On Wed, May 4, 2011 at 17:46, Angus Robertson - Magenta Systems Ltd <
an...@magsys.co.uk> wrote:
> > Actually I tested it with our application
>
> If you publish the source of that application with build instructions, we
> will then be able to test it as well.
>
I do not think we can provi
If this is HTML related, why you use "XML" in the names?!
Why not use the faster, and memory efficient, HTTPApp.pas code methods?
Ok, I took your example and created a (I suppose) complete encode-decode
unit.
Daniele
--
To unsubscribe or change your settings for TWSocket mailing list
please go
> Actually I tested it with our application
If you publish the source of that application with build instructions, we
will then be able to test it as well.
Or add the funcionality to the web server component and demo, which is
what we will have to do to test it.
Angus
--
To unsubscribe or cha
Actually I tested it with our application and ICS multi-part HTTP downloader
demo.
Regards,
SZ
On Wed, May 4, 2011 at 11:25, Angus Robertson - Magenta Systems Ltd <
an...@magsys.co.uk> wrote:
> > Please add this to SVN.
>
> As I said yesterday, I will look at this when it can be properly tested
Ok, I took your example and created a (I suppose) complete encode-decode
unit.
Daniele
*
unit XmlParserUnit;
interface
uses StrUtils, SysUtils;
const
XmlNames : Array[1..240] of String = ('"', ''', '&
marius gabi wrote:
> Arno, in this moment the client sends the entire certificates chain:
> 1. its client certificate issued by the intermediary CA (2 from
> bellow)
> 2. intermediary certificate issued by the root CA
> 3. root CA
OK.
>
> The only certificate that is common between our server c
> Please add this to SVN.
As I said yesterday, I will look at this when it can be properly tested
using an ICS component or demo application. We don't release untested
code.
You don't need to post any more code, it's a simple change to support
ranges in a stream.
Angus
--
To unsubscribe or c
Arno, in this moment the client sends the entire certificates chain:
1. its client certificate issued by the intermediary CA (2 from bellow)
2. intermediary certificate issued by the root CA
3. root CA
The only certificate that is common between our server chain and client chain
is (3) root CA.
Arno Garrels wrote:
> Usually all CA certificates issued by a root
> CA are available for download as well.
Correction: That is mostly true if they have been
issued to their own organizition.
> In your case the URL is
> http://sumo.irisa.fr/html/pki/ but their server currently fails
> with error
marius gabi wrote:
> Thank you for your prompt response. We already tried your solution
> and seems to be working. The issue is as follows: I do not have
> (access to) the client's certificate (application not developed by
> me) in order to compose the chains you mentioned.
You do not need client
Hello,
Somehow Delphi could not link with two functions so here is my solution:
procedure ZlibCompressStreamEx( InStream, OutStream: TStream;
NumLevel: Integer;
StreamType : TZStreamType;
UseDirectOut:
Thank you for your prompt response. We already tried your solution and seems to
be working. The issue is as follows: I do not have (access to) the client's
certificate (application not developed by me) in order to compose the chains
you mentioned. Furthermore I aspect that other clients that hav
marius gabi wrote:
> Thank you for your feedback.In my current scenario the certificate
> structure is as follows:
> Server(my application) | Client
> Root certificate -same as- Root certificate
> Intermediary CA-not same as- Intermediary CA
> Server Cert -not same as- Client Cert
>
15 matches
Mail list logo