|
|
| Author |
Message |
|
| seancharles |
 Posted: Wed Aug 15, 2007 9:27 pm |
 |
|
|
User
Joined: 18 Jul 2007
Posts: 57
|
Here's the workflow that seems to cause problems:
Start browser.
Start yaws (+yaws session server).
Go to home page
Session start: new_session_cookie()
halt() the system.
Restart the system.
Refresh my page.
BANG!
As the session server has restarted it naturally loses all knowledge of any sessions it has dished out cookies for and so when the browser sends it back, all I get instead of my home page is this:
Code:
Internal error, yaws code crashed
yaws code at appmod:0 crashed or ret bad val:110
Req: {http_request,'GET',{abs_path,"/p/1"},{1,1}}
If I manually delete the cookie from within Firefox, restart the system and then try again everything is fine.
So, is it a bug (I make this accusation with the greatest of respect!) in yaws or have I just f**&#^#-d up again >
Sean Charles. |
|
|
| Back to top |
 
|
| seancharles |
| Posted: Wed Aug 15, 2007 9:34 pm |
|
|
|
User
Joined: 18 Jul 2007
Posts: 57
|
It's my fault.
No, don't be surprised.
It has something to do with what I am passing back, I am sure I'll sort it out. I know that the setcookie() hands back
{header, ... }
which needs to be part of the response, the problem (as usual) is my code: when the cookie is *new* it works, when the cookie is already alive, I must be handing back something that yaws don't like.
My fault.
Sorry forums!
|
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
