hi,
if I understand your problem well, the e-mail submits a form to the site? I
think the browser does not open because it receives a response... it opens
because you are submitting something, just like if you click on a link in
Outlook. Even if the page at the other end were a pure html, it would do the
same. (as I understand it) So your server can't do anything about it. it's
the client app that must be changed.
I hope it helps
ThunderMusic
"RobGMiller" <Ro********@gmail.comwrote in message
news:11**********************@m58g2000cwm.googlegr oups.com...
On Feb 28, 9:20 am, "Steve B." <steve_bea...@com.msn.swapwrote:
If I've correclty understood your question, you will probably have to deal
with JavaScript to create a request to the server. This request will
points
to a custom handler (ashx files are good for that), and since it will be
run
from the javascript code, the page won't post back.
Steve
"RobGMiller" <RobGMil...@gmail.coma écrit dans le message de news:
1172678875.324887.288...@h3g2000cwc.googlegroups.c om...
Using ASP.NET 2.0
Need to simply process incoming postback information without sending
back a reponse.
Client sends HTML from application other than a browser to a page on a
web site. Web Server ASP generates a response page and send it back
which opens the browser on the client.
How to avoid sending back the response page.
Thanks,
RobGMiller.........- Hide quoted text -
- Show quoted text -
The postback is sent from an email message containing HTML.
<html><body><form method='GET' action = " http:\\website\page.aspx'"
& HTMLFormContent & " Record Name: <input name='RecordName' / <input
type='submit' value='Submit'</form></body></html>
When the submit button is clicked from the body of the email, the web
browser opens.
I believe the postback is sent to page.aspx from the client computer
and the browser opens on the client computer as a response to
receiving the dynamic page returned from the server because if
something different than the email html is added to page.aspx this new
html showes up in the browser.
Ideally page.aspx will contain some kind of instruction that will
prevent the server and or ASP.NET from sending it back to the client
and then the web browser will not open or the instruction can be sent
from the client.
Can a web server session be ended with a command from the client for
instance. This could be sent along with the PostBack perhaps.
