Opened 14 years ago

Closed 14 years ago

#2876 closed defect (fixed)

[witch patch, positive review] sage/server/notebook/twist.py doctest fails when dsage certificates are not present

Reported by: yi Owned by: boothby
Priority: major Milestone: sage-3.0
Component: notebook Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

Since it's trying to use https, the notebook object will try to generate a self signed certificate when one is not present already. This doesn't work with doctesting since we can't expect user interaction. The fix switches the notebook server to use http instead. It looks like robert did a good job of disabling creating accounts so I don't see any new security holes created by this.

Attachments (1)

simple_server_doctest.patch (5.1 KB) - added by yi 14 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 14 years ago by yi

  • Summary changed from sage/server/notebook/twist.py doctest fails when dsage certificates are not present to [witch patch, needs review] sage/server/notebook/twist.py doctest fails when dsage certificates are not present

comment:2 Changed 14 years ago by yi

Cwitty pointed out that if you use the secure=False option, one gets logged on automatically. Does anyone know of an easy way to turn that feature off when doctesting?

Changed 14 years ago by yi

comment:3 Changed 14 years ago by was

  • Summary changed from [witch patch, needs review] sage/server/notebook/twist.py doctest fails when dsage certificates are not present to [witch patch, positive review] sage/server/notebook/twist.py doctest fails when dsage certificates are not present

Works perfectly.

comment:4 Changed 14 years ago by mabshoff

  • Resolution set to fixed
  • Status changed from new to closed

Merged in Sage 3.0.alpha4

Note: See TracTickets for help on using tickets.