I'd guess the '&' should really be
    test/test_ppg -q "http://127.0.0.1:8080?username=foo&password=bar si.txt 
notify.txt"

    or

    test/test_ppg -q "http://127.0.0.1:8080?username=foo&password=bar"; si.txt 
notify.txt

The '&' causes me some concern.  Note though that I've never run PPG.

If it isn't that, maybe you are trying to post XML content with an HTML
tag; your HTML tag should be this:

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>

Though it seems that that HTML tag is coming from the remote server... I
dunno.  Just some suggestions.

Beckman

On Fri, 16 Apr 2004, Harish Kumar wrote:

>
> Hi,
>  V r trying to run the test_ppg after running the bearerbox and wapbox for
> PPG service as per the userguide. When the command test/test_ppg -q
> http://127.0.0.1:8080?username=foo'&'password=bar si.txt notify.txt is tried
> out, the following is the trace that come on the screen with errors
> =========================================================================
> [EMAIL PROTECTED] gateway-1.2.1]# test/test_ppg -q
> http://127.0.0.1:8080?username=foo'&'password=bar si.txt notify.txt
> 2004-04-16 12:28:16 [0] INFO: an input without a configuration file assumed
> 2004-04-16 12:28:16 [0] DEBUG: using si.txt as a content file
> 2004-04-16 12:28:16 [0] DEBUG: using notify.txt as a control file
> 2004-04-16 12:28:16 [0] DEBUG: Started thread 1
> (test/test_ppg.c:push_thread)
> 2004-04-16 12:28:16 [1] DEBUG: TEST_PPG: starting to push job 0
> 2004-04-16 12:28:16 [1] DEBUG: Started thread 2 (gwlib/fdset.c:poller)
> 2004-04-16 12:28:16 [1] DEBUG: Started thread 3
> (gwlib/http.c:write_request_thread)
> 2004-04-16 12:28:16 [1] DEBUG: push done
> 2004-04-16 12:28:16 [3] DEBUG: HTTP: Opening connection to `127.0.0.1:8080'
> (fd=13).
> 2004-04-16 12:28:16 [3] DEBUG: HTTP: Sending request:
> 2004-04-16 12:28:16 [3] DEBUG: Octet string at 0x80c4778:
> 2004-04-16 12:28:16 [3] DEBUG:   len:  1266
> 2004-04-16 12:28:16 [3] DEBUG:   size: 1267
> 2004-04-16 12:28:16 [3] DEBUG:   immutable: 0
> 2004-04-16 12:28:16 [3] DEBUG:   data: 50 4f 53 54 20 2f 20 48   POST / H
> 2004-04-16 12:28:16 [3] DEBUG:   data: 54 54 50 2f 31 2e 31 0d   TTP/1.1.
> 2004-04-16 12:28:16 [1] DEBUG: TEST_PPG: push 0 done: reply from,
> http://127.0.0.1:8080?username=foo&password=bar
> Entity: line 1: error: Space required after the Public Identifier
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>                                                 ^
> Entity: line 1: error: SystemLiteral " or ' expected
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>                                                 ^
> Entity: line 1: error: xmlParseExternalID: PUBLIC, no URI
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>                                                 ^
> Entity: line 9: error: Opening and ending tag mismatch: HR and BODY
> </BODY></HTML>
>        ^
> Entity: line 9: error: Opening and ending tag mismatch: P and HTML
> </BODY></HTML>
>               ^
> Entity: line 9: error: Premature end of data in tag <BODY>
> <H1>Method Not Allowed<
> </BODY></HTML>
>               ^
> Entity: line 9: error: Premature end of data in tag er at arabic.witl.com
> Port 80<
> </BODY></HTML>
>               ^
> 2004-04-16 12:28:16 [1] WARNING: PAP COMPILER: pap_compile: parse error in
> pap source
> 2004-04-16 12:28:16 [1] WARNING: TEST_PPG: receive_push_reply: cannot
> compile pap message
> 2004-04-16 12:28:16 [1] INFO: TEST_PPG: In thread 1 0 succeeded, 1 failed
> 2004-04-16 12:28:16 [1] DEBUG: Thread 1 (test/test_ppg.c:push_thread)
> terminates.
> 2004-04-16 12:28:16 [0] INFO: TEST_PPG: 1 requests in 0.000000 seconds, inf
> requests per second
> 2004-04-16 12:28:16 [0] DEBUG: Waiting for 3
> (gwlib/http.c:write_request_thread) to terminate

---------------------------------------------------------------------------
Peter Beckman                                                  Internet Guy
[EMAIL PROTECTED]                             http://www.purplecow.com/
---------------------------------------------------------------------------

Reply via email to