[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HTTP BAD Request
Assuming you mean the HTTPAPI debug log file, use command WRKLNK
'/tmp' and press enter. Then, search for text file httpapi_debug.txt.
If you don't see it, it is likely due to not having debugging enabled
within HTTPAPI inside your application. Do this in your code by
calling procedure http_debug(*on) prior to doing any other HTTPAPI
calls. You can (optionally) provide a different name and location for
the debug log file by specifying that as the second parameter to
http_debug().
On Tue, Mar 2, 2010 at 8:58 AM, Zimmerman, Donald W.
<[1]donald.zimmerman@xxxxxxxxxxxxxx> wrote:
I am receiving a bad request and I have looked at the XML up and
down
and see nothing wrong. I am unsure how to display the debug
statements
as I see in many other questions. Can someone easily tell me how
this
is accomplished?
Notice: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL OR PROPRIETARY
INFORMATION, INCLUDING PATIENT HEALTH INFORMATION THAT IS
PROTECTED
UNDER HIPAA AND OTHER STATE AND FEDERAL CONFIDENTIALITY LAWS.
PLEASE
DELIVER IMMEDIATELY ONLY TO THE INTENDED RECIPIENT. IF THIS
TRANSMISSION WAS RECEIVED IN ERROR, PLEASE CONTACT THE SENDER
IMMEDIATELY AND DO NOT DISTRIBUTE THE INFORMATION TO ANY OTHER
PERSON.
-------------------------------------------------------------------
----
This is the FTPAPI mailing list. To unsubscribe, please go to:
[2]http://www.scottklement.com/mailman/listinfo/ftpapi
-------------------------------------------------------------------
----
References
1. mailto:donald.zimmerman@xxxxxxxxxxxxxx
2. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------