Kbase P28374: How to debug a returned blank page in Webspeed?
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  11/25/2003 |
|
Status: Unverified
GOAL:
How to debug a returned blank page in Webspeed?
FACT(s) (Environment):
WebSpeed 3.x
FIX:
When the Webspeed Server receives a request it processes the .R and returns data to the client in a stream as it processes. When an error occurs it stops processing and closes the stream. If you receive a blank page or a half-processed page that means an error has occurred and it only processed up to this point.
If the returned page does have some data in it, look to the last piece of code it processed in your Webspeed file. Usually it is easy to see where the error occurred if you have some HTML at the start of this application before your speedscript begins. Usually if you choose View Source in your browser you can see exactly the last code sent to the stream. Ignore the closing </Body> & </HTML> tags because those are done automatically.
If the returned page is totally blank your error could be in the HEAD of the document and errors upon the initial processing. I good way to debug this is to add a line of debugging text such as;
We are here and variable1 = `var1` variable2 = `var2`
This way you can see not only how far it is processing up to but current values of the variables you are using within your application to see if the error is due to a record not being in the buffer or if it is being called / processed in an improper format.