Emmanuel Engelhart | 15 Nov 13:07 2014

Questions about Parsoid caching HTTP headers

Hi

I currently try to create a cache for "mwoffliner". A cache for images 
(thumbnails) and a cache for Parsoid output. For the images/thumbnails 
it's pretty straight forward thanks to the "last-modified" header.

Unfortunately, for the Parsoid output, this seems to be more 
complicated. Gabriel's htmldumper relies only on the oldid value, but 
I'm not really satisfied byt this approach because I want to be able to 
download a new version of the HTML for the same oldid if necessary (for 
example if the HTML output was improved with a Parsoid fix).

There is an "age" header but I don't really understand the fundamental 
difference with "last-modified". Do we have the same information here 
but presented in an other way? If yes, why is that better than 
"last-modified"?

There is in addition the "x-varnish" header but this is IMO an internal 
information I should not rely on (and BTW, time to time we get headers 
with two "x-warning" header entries, what looks pretty weird to me - see 
PS).

Finally my question, might we introduce a "last-modified" HTTP header?

Regards
Emmanuel

PS: Here an example of request with two "x-varnish" headers:

$ curl -I 
(Continue reading)

Andre Klapper | 3 Nov 14:18 2014
Picon

Google Code-In 2014: Become a mentor and add tasks!

Hi Parsoid & VisualEditor crew,

Google Code-In (GCI) will soon take place again - a contest for 13-17
year old students to contribute to free software projects. 

Wikimedia wants to take part again. 
Last year's GCI results were surprisingly good - see
https://www.mediawiki.org/wiki/Google_Code-in_2013

We need your help:

1) Go to 
https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and
read the information there. If something is unclear, ask!

2) Add yourself to the table of mentors on 
https://www.mediawiki.org/wiki/Google_Code-in_2014#Contacting_Wikimedia_mentors
- the more mentors are listed the better our chances are that Google
accepts us.

3) Please take ten minutes and go through open recent tickets in
https://bugzilla.wikimedia.org in your area of interest. If you see
self-contained, non-controversial issues with a clear approach which you
can recommend to new developers and would mentor: Add the task to
https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks

Until Sunday November 12th, we need at least five tasks from each of
these categories (plus some less technical beginner tasks as well):
* Code: Tasks related to writing or refactoring code
* Documentation/Training: Tasks related to creating/editing documents
(Continue reading)

Chris Croome | 17 Jun 14:40 2014
Picon

Problems after switching to the .deb version of parsoid

Hi

I maintain the server running the wiki at
https://wiki.transitionnetwork.org/ and 3 month ago it was upgraded to
MediaWiki 1.22.x and the VisualEditor was installed from source and that
was quite straight forward, details here:

- https://trac.transitionnetwork.org/trac/ticket/706

Yesterday I upgraded to MediaWiki 1.23.0 and switched to using the
Debian repo for parsoid as per:

- https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian

And since then I have been unable to get the VisualEditor working, when
you click on 'Edit' nothing happens, looking at the HTTP requests there
is a GET to load.php and a 304 in response but nothing actually happens
in the web browser, I have tried with Firefox 30 and the Debian Wheezy
Chromium.

There is nothing of note in the webserver logs or the parsoid.log.

It appears to be working correctly on the command line:

  curl http://localhost:8142/localhost/Sandbox -d wt="Hello ''world''" -d body=1
    <body data-parsoid='{"dsr":[0,15,0,0]}'><p data-parsoid='{"dsr":[0,15,0,0]}'>Hello <i data-parsoid='{"dsr":[6,15,2,2]}'>world</i></p></body>

I'm not sure what to try next.

More details including the Nginx config can be found on the comments I
(Continue reading)

Pratik Lahoti | 9 Jun 19:37 2014
Picon

Markup cleansing by clearing all linguistic elements

Hi,

I am working on the mass migration tools project as a part of Google Summer of Code. One of the parts of project is to import old translations into the Translate Extension.

We are done with a basic import by splitting the old pages on double newlines (\n\n) and some more alignment based on h2 headers. We are now thinking of improving the alignment.

Is there some work done on the subject mentioned? For each of the unit, what I would like to do is clear all the linguistic elements and have the bare markup left. Then, I could compare the markup of the source and target units and align accordingly.

Are there any API's available which already do this? Please guide me to accomplish this task.

--
Warm Regards,
Pratik Lahoti
GSoC Intern | Wikimedia
User:BPositive

_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Fraifrai | 19 May 11:03 2014
Picon

Using Parsoid with a wiki presenting a self-signed certificate

Hi,

I put an internal wiki under HTTPS to prevent clear password transmissions and modified the ad hoc  parsoidConfig.setInterwiki entry to https.

Parsoid seems to refuse the self-signed certificate presented by the wiki :

ERROR in wikie7ar:Accueil with oldid: 10928
Stack trace: DoesNotExistError: Page Fetch failure for null : Error: DEPTH_ZERO_SELF_SIGNED_CERT
worker 8536 died (1), restarting.

How can I tell Parsoid to accept such certificates ?

Cheers,

 

-- -- Fraifrai http://www.fraifrai.net Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org
_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Andreas Brill | 2 Apr 11:17 2014

Re: Persoid with nginx and https

Dear all,

I impemented node.js / parsoid and nginx and are able to access the mediawiki via https 443.

But when I use the button edit which appeared after I implemented visual editor I got the following error message:

 

Error loading data from server: parsoidserver-http-curl-error: Peer certificate cannot be authenticated with known CA certificates. Would you like to retry?

 

This is an “self-made” certificate and not signed by an official company. Can you help me to allow this communication.

 

Kind regards

Andreas Brill

 


Utimaco Safeware AG

Seat: Aachen – Registergericht Aachen HRB 17938
WEEE-Reg.No.: DE39805015
Managementboard: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO
Supervisory Board: Katrin Wehr-Seiter (Chairman)



Utimaco Safeware AG

Seat: Aachen – Registergericht Aachen HRB 17938
WEEE-Reg.No.: DE39805015
Managementboard: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO
Supervisory Board: Katrin Wehr-Seiter (Chairman)
_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Federico Leva (Nemo | 16 Mar 21:49 2014
Picon

Have multiline tags not terminate the list item until the tag is terminated

Lists in wikitext are a pain. Proof: number of duplicates of 
<https://bugzilla.wikimedia.org/1581>.
Aryeh Gregor proposed in 2007 an amendment that would IMHO solve many 
problems and find no opposers in principle, "Have multiline tags not 
terminate the list item until the tag is terminated": 
<https://bugzilla.wikimedia.org/show_bug.cgi?id=9996#c5>
Does someone disagree? How hard is it to implement? (Probably rather or 
very hard, but who knows.)

For more general context of how I was brought to this problem, and to 
discuss alternative solutions  for my specific issue, please refer to 
<https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions> 
instead.

Nemo

_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Gabriel Wicke | 8 Jan 21:37 2014
Picon

DOM spec input wanted: Can we do without explicit link types?

Hi,

I'd like to ask you for your input on a change to the DOM spec [1] we
are considering. The idea is to simplify links by removing the explicit
mw:WikiLink or mw:ExtLink typeof attributes:

  <a rel="mw:WikiLink" href="./Main_Page">Main Page</a>
  <a rel="mw:ExtLink" href="http://example.com">http://example.com</a>

would become just

  <a href="Main_Page">Main Page</a>
  <a href="http://example.com">http://example.com</a>

Reasons for this change are:

- The external vs. internal link distinction is pretty simple to do
  with a prefix match on the href.

- When editing, an internal link can turn into an external one and
  vice-versa. Editors should not have to deal with updating the typeof
  to reflect the information already available in the href attribute.

- The page source will be slightly cleaner and smaller.

Potential disadvantages we see are

- For ISBN links [2], we will continue to link to Special:BookSources,
  which looks internal. Matching on that to identify ISBN links should
  however not be harder than it is right now.

Are you currently relying on these typeofs? Do you see other issues with
this proposed change?

Thanks for your input,

Gabriel

[1]: https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Wiki_links

_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Thomas Gulli | 14 Dec 22:12 2013
Picon

Re: Problems installing Parsoid

Aha,  I understand! Thanks you very much! I really appreciate it!

One last question; Is it possible to install git on a webhosting I have at example hostgator.com?

From: amir.aharoni <at> mail.huji.ac.il
Date: Sat, 14 Dec 2013 23:10:26 +0200
To: wikitext-l <at> lists.wikimedia.org
Subject: Re: [Wikitext-l] Problems installing Parsoid

> Yes, but I do not understand "parsoid/api" and the anonymous checkout thing.

parsoid/api is just the name of a directory in the parsoid source tree.

"Checkout" refers to getting the Parsoid code from Gerrit, which is MediaWiki's source repository. Very simply, you need to run this command on your server:
git clone https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid

This will create a parsoid directory and download the source there.

You need to have git installed before that.

If you are curious, you can find more details about how we store our source code here:
https://www.mediawiki.org/wiki/Gerrit

> it possible to install this on when the wiki is not host on my computer, but at a third-party?

If you are able to run shell commands and install some software on that server, then it should be possible.


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬

2013/12/14 Thomas Gulli <tgg <at> live.no>
Yes, but I do not understand "parsoid/api" and the anonymous checkout thing.

From: amir.aharoni <at> mail.huji.ac.il
Date: Sat, 14 Dec 2013 22:42:33 +0200
To: wikitext-l <at> lists.wikimedia.org
Subject: Re: [Wikitext-l] Problems installing Parsoid




--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬


2013/12/14 Thomas Gulli <tgg <at> live.no>
Hi,

I do not understand how I could install Parsoid on the web server so I could use the new visual editor. I would really appreciate help with this.

Regards,
Thomas Gulli

_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l



_______________________________________________ Wikitext-l mailing list Wikitext-l <at> lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitext-l

_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l



_______________________________________________ Wikitext-l mailing list Wikitext-l <at> lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitext-l
_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Thomas Gulli | 14 Dec 21:37 2013
Picon

Problems installing Parsoid

Hi,

I do not understand how I could install Parsoid on the web server so I could use the new visual editor. I would really appreciate help with this.

Regards,
Thomas Gulli
_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
Emmanuel Engelhart | 2 Dec 13:30 2013

Parsoid farm HTTP 500 errors

Hi

Currently happening with pretty much different URLs.

For example:
* http://208.80.154.248/enwiki/%2F%5C?oldid=535552102
* http://208.80.154.248/enwiki/%2Fr%2F?oldid=570334525

Regards
Emmanuel

--
Kiwix - Wikipedia Offline & more
* Web: http://www.kiwix.org
* Twitter: https://twitter.com/KiwixOffline
* more: http://www.kiwix.org/wiki/Communication

_______________________________________________
Wikitext-l mailing list
Wikitext-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l

Gmane