Thank you, Richard. I think I understand now... I experienced this HTML
behavior when trying to "debug" this problem, but figured it had little
to do with the problem. HTML coming up in that page (even the pdf, as
garble) was not producing a warning... Now I understand.
One last question, thoug
>get data is insecure by nature so the whole page is insecure and no
>warnings, as soon as you post you invoke the security.
No, no, no.
POST data is *NO* *MORE* *SECURE* than GET data! Period.
Okay, if you want to get picuyane -- A total idiot user can read the URL in
their location bar, and
>> >The GET method form works fine, while the POST method (which is what I
>> >need to use) pops up a message about the page containing both secure and
>> >nonsecure data.
>> >
>> >WTF?
>>
>> Well, the new browser window opens, but you're loading a PDF, not HTML, so
>> it's not really getting any
>https://my.server/reports.php"; method="post"
>target="_blank">
>
>
>https://my.server/reports.php"; method="get"
>target="_blank">
>
>
>
>These forms are identical with the exception of the post/get methods.
>
>A PDF file is being dynamically generated and displayed in a pop-up.
>
>The GET metho
4 matches
Mail list logo
